Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
The programmer's brain - By Felienne Hermans
Search
Sponsored
·
SiteGround - Reliable hosting with speed, security, and support you can count on.
→
Marabesi
January 21, 2022
Technology
940
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
The programmer's brain - By Felienne Hermans
Marabesi
January 21, 2022
More Decks by Marabesi
See All by Marabesi
Software Metrics Machine
marabesi
0
28
CISTI 2026 - Test-Driven Development Versus Test Smells: An Empirical Study With Students From UFABC University
marabesi
0
43
A comprehensive view of refactoring
marabesi
0
1.2k
Explorando la conexión entre test smells y la práctica del TDD - GRIAL - research group
marabesi
0
63
Una introducción a eXtreme Programming
marabesi
0
170
TDD anti patterns - episode 6 - with Ignacio Saporitti and Pablo Díaz
marabesi
0
590
TDD anti patterns - episode 5 - with Sofia Carballo and Juan Pablo
marabesi
0
590
TDD anti patterns - episode 4 - with Javier Martínez
marabesi
0
680
TDD anti patterns - episode 3 - With Juan Pablo
marabesi
0
740
Other Decks in Technology
See All in Technology
AI駆動開発をチームに根付かせる - 「1行も書かない」チームがHarnessを育てた1年 -
kenichirokimura
2
290
AI駆動開発を組織で促すために
lycorptech_jp
PRO
1
2.4k
形式手法特論:Hyperproperty とモデル検査 #kernelvm / Kernel VM Study Tokyo 19th
ytaka23
0
810
OpenID for Verifiable Credentials 実装から見えた相互運用性確保までの道のり(OAuth/OIDC Numa (Immersion) Workshop 2026)
oidfj
PRO
0
280
あなたの知らないバージョン命名規則
sat
PRO
2
760
Contract One Engineering Unit 紹介資料
sansan33
PRO
0
20k
コミュニティから始まった農業IoTとの7年間 ——人との関わりが教えてくれたこと
peacemaker07
0
110
サイボウズ 開発本部採用ピッチ / Cybozu Engineer Recruit
cybozuinsideout
PRO
12
85k
Android skills に学ぶ
kokiko
0
180
Windows の互換機能 - 古いプログラムはなぜ動作できるのか
murachiakira
PRO
0
110
三人寄ればチューリング完全
puhitaku
6
3.2k
GopherCon @シアトル に行ってきました
logica0419
0
270
Featured
See All Featured
The World Runs on Bad Software
bkeepers
PRO
72
12k
Ethics towards AI in product and experience design
skipperchong
2
350
Fantastic passwords and where to find them - at NoRuKo
philnash
52
3.8k
Facilitating Awesome Meetings
lara
57
7.1k
Amusing Abliteration
ianozsvald
1
260
HDC tutorial
michielstock
2
820
How to Think Like a Performance Engineer
csswizardry
28
2.7k
StorybookのUI Testing Handbookを読んだ
zakiyama
31
6.9k
Connecting the Dots Between Site Speed, User Experience & Your Business [WebExpo 2025]
tammyeverts
11
1k
How To Speak Unicorn (iThemes Webinar)
marktimemedia
1
560
Believing is Seeing
oripsolob
1
200
How GitHub (no longer) Works
holman
316
150k
Transcript
The programmer's brain By Felienne Hermans
Hello there - This is a book is the intersection
between learning and tech.
Agenda What's the idea: Go over the following sections: 1.
The memory 2. Reading code 3. Writing code 4. Naming
1. The memory
Memory classification - Working memory - Short term memory -
Long term memory
Memory classification - Working memory - Short term memory -
Long term memory * The magical number seven minus or plus two
SPACED REPETITION, REVISIT
Cognitive refactoring - Grab a piece of code - Place
that where you need - Remove that afterwards
2. Reading code
Code - Reading texts and reading code are strongly related
- Same parts of the brain are active - The first is that research shows we as programmers spend more time on reading code than writing
Code - Reading texts and reading code are strongly related
- Same parts of the brain are active - The first is that research shows we as programmers spend more time on reading code than writing it * lack of practicing on reading code
3. Naming
Naming - Names make up a large part of the
code base - Names play a role in code reviews - Names are the most accessible form of documentation - Names can serve as beacons
Naming - Names make up a large part of the
code base - Names play a role in code reviews - Names are the most accessible form of documentation - Names can serve as beacons * Linking chuks
W.M → L.T.M L.T.M → W.M
Naming she refers a research that points to 19% increase
on finding defects for code that does is not abbreviated.
4. Writing code
Writing - an interrupted task takes longer to finish compared
to a uninterrupted on, this is what research points to.
FlowLight Manuela Züger
https://andre-meyer.ch/flowlight
https://andre-meyer.ch/flowlight
https://andre-meyer.ch/flowlight
Writing - TODO's in code remain unresolved for long time
- People cannot multitask - static-types systems outperform dynamic ones in terms of time and accuracy finding bugs
The programmer's brain By Felienne Hermans