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
Marabesi
January 21, 2022
Technology
0
630
The programmer's brain - By Felienne Hermans
Marabesi
January 21, 2022
Tweet
Share
More Decks by Marabesi
See All by Marabesi
A comprehensive view of refactoring
marabesi
0
970
Explorando la conexión entre test smells y la práctica del TDD - GRIAL - research group
marabesi
0
35
Una introducción a eXtreme Programming
marabesi
0
89
TDD anti patterns - episode 6 - with Ignacio Saporitti and Pablo Díaz
marabesi
0
420
TDD anti patterns - episode 5 - with Sofia Carballo and Juan Pablo
marabesi
0
360
TDD anti patterns - episode 4 - with Javier Martínez
marabesi
0
520
TDD anti patterns - episode 3 - With Juan Pablo
marabesi
0
600
TDD anti patterns - episode 2 - TDD anti patterns - With Giulio Perrone
marabesi
0
680
Tips for improving test assertions at Codurance
marabesi
0
1.2k
Other Decks in Technology
See All in Technology
B2C&B2B&社内向けサービスを抱える開発組織におけるサービス価値を最大化するイニシアチブ管理
belongadmin
1
6.8k
Claude Code に プロジェクト管理やらせたみた
unson
6
3.9k
マネジメントって難しい、けどおもしろい / Management is tough, but fun! #em_findy
ar_tama
7
1.1k
AIの全社活用を推進するための安全なレールを敷いた話
shoheimitani
2
510
敢えて生成AIを使わないマネジメント業務
kzkmaeda
2
440
Beyond Kaniko: Navigating Unprivileged Container Image Creation
f30
0
130
KiCadでPad on Viaの基板作ってみた
iotengineer22
0
300
事業成長の裏側:エンジニア組織と開発生産性の進化 / 20250703 Rinto Ikenoue
shift_evolve
PRO
2
21k
Delta airlines®️ USA Contact Numbers: Complete 2025 Support Guide
airtravelguide
0
340
さくらのIaaS基盤のモニタリングとOpenTelemetry/OSC Hokkaido 2025
fujiwara3
3
430
成長し続けるアプリのためのテストと設計の関係、そして意思決定の記録。
sansantech
PRO
0
120
American airlines ®️ USA Contact Numbers: Complete 2025 Support Guide
airhelpsupport
0
380
Featured
See All Featured
Navigating Team Friction
lara
187
15k
BBQ
matthewcrist
89
9.7k
Automating Front-end Workflow
addyosmani
1370
200k
Responsive Adventures: Dirty Tricks From The Dark Corners of Front-End
smashingmag
251
21k
Raft: Consensus for Rubyists
vanstee
140
7k
Building Flexible Design Systems
yeseniaperezcruz
328
39k
The Straight Up "How To Draw Better" Workshop
denniskardys
234
140k
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
656
60k
Being A Developer After 40
akosma
90
590k
The Illustrated Children's Guide to Kubernetes
chrisshort
48
50k
Learning to Love Humans: Emotional Interface Design
aarron
273
40k
Six Lessons from altMBA
skipperchong
28
3.9k
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