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
·
Ship Features Fearlessly
Turn features on and off without deploys. Used by thousands of Ruby developers.
→
Marabesi
January 21, 2022
Technology
950
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
29
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
600
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
Data Hubグループ 紹介資料
sansan33
PRO
0
3.2k
Sansan Engineering Unit 紹介資料
sansan33
PRO
1
5k
Genie Code ワークショップ 基礎編 / Genie-Code-Workshop-fundamental
databricksjapan
PRO
0
290
Master Dataグループ紹介資料
sansan33
PRO
1
4.9k
Continuous Delivery! It is not what you think it is
tdpauw
0
130
Driving AI Adoption Using In-House GPUs to Serve Qwen
po3rin
1
290
DMMブックスのNext.js化を加速させるAI活用 / Migrating DMM Books to Next.js with AI
kentarom
1
300
Kiro5兄弟のいまどきのセキュリティ基礎知識
kentapapa
0
500
Sony-DroidKaigi2026
sony
0
260
アクセスキー流出時の対応で再認識した攻撃側と防御側の非対称性について
kazzpapa3
1
510
AI時代におけるプロダクト横断勉強会の設計
zozotech
PRO
0
110
データエンジニアの困りごとをDevinと一緒に解消する
10xinc
2
300
Featured
See All Featured
Producing Creativity
orderedlist
PRO
348
41k
Ethics towards AI in product and experience design
skipperchong
2
360
KATA
mclloyd
PRO
35
15k
It's Worth the Effort
3n
188
29k
How Software Deployment tools have changed in the past 20 years
geshan
1
34k
職位にかかわらず全員がリーダーシップを発揮するチーム作り / Building a team where everyone can demonstrate leadership regardless of position
madoxten
69
64k
Leveraging LLMs for student feedback in introductory data science courses - posit::conf(2025)
minecr
1
370
How to Grow Your eCommerce with AI & Automation
katarinadahlin
PRO
1
260
Keith and Marios Guide to Fast Websites
keithpitt
413
23k
Learning to Love Humans: Emotional Interface Design
aarron
275
41k
Neural Spatial Audio Processing for Sound Field Analysis and Control
skoyamalab
0
440
Organizational Design Perspectives: An Ontology of Organizational Design Elements
kimpetersen
PRO
1
810
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