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
560
The programmer's brain - By Felienne Hermans
Marabesi
January 21, 2022
Tweet
Share
More Decks by Marabesi
See All by Marabesi
Explorando la conexión entre test smells y la práctica del TDD - GRIAL - research group
marabesi
0
22
Una introducción a eXtreme Programming
marabesi
0
47
TDD anti patterns - episode 6 - with Ignacio Saporitti and Pablo Díaz
marabesi
0
380
TDD anti patterns - episode 5 - with Sofia Carballo and Juan Pablo
marabesi
0
320
TDD anti patterns - episode 4 - with Javier Martínez
marabesi
0
470
TDD anti patterns - episode 3 - With Juan Pablo
marabesi
0
530
TDD anti patterns - episode 2 - TDD anti patterns - With Giulio Perrone
marabesi
0
610
Tips for improving test assertions at Codurance
marabesi
0
1.1k
TDD anti-patterns at Codurance Spain
marabesi
0
1.9k
Other Decks in Technology
See All in Technology
#TRG24 / David Cuartielles / Post Open Source
tarugoconf
0
580
Godot Engineについて調べてみた
unsoluble_sugar
0
380
【JAWS-UG大阪 reInvent reCap LT大会 サンバが始まったら強制終了】“1分”で初めてのソロ参戦reInventを数字で振り返りながら反省する
ttelltte
0
140
embedパッケージを深掘りする / Deep Dive into embed Package in Go
task4233
1
210
PaaSの歴史と、 アプリケーションプラットフォームのこれから
jacopen
7
1.4k
Alignment and Autonomy in Cybozu - 300人の開発組織でアラインメントと自律性を両立させるアジャイルな組織運営 / RSGT2025
ama_ch
1
2.4k
Evolving Architecture
rainerhahnekamp
3
250
AWSマルチアカウント統制環境のすゝめ / 20250115 Mitsutoshi Matsuo
shift_evolve
0
110
When Windows Meets Kubernetes…
pichuang
0
300
JuliaTokaiとJuliaLangJaの紹介 for NGK2025S
antimon2
1
110
Reactフレームワークプロダクトを モバイルアプリにして、もっと便利に。 ユーザに価値を届けよう。/React Framework with Capacitor
rdlabo
0
120
2025年の挑戦 コーポレートエンジニアの技術広報/techpr5
nishiuma
0
140
Featured
See All Featured
Designing for Performance
lara
604
68k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
PRO
10
860
Understanding Cognitive Biases in Performance Measurement
bluesmoon
27
1.5k
Build The Right Thing And Hit Your Dates
maggiecrowley
33
2.5k
Scaling GitHub
holman
459
140k
We Have a Design System, Now What?
morganepeng
51
7.3k
Performance Is Good for Brains [We Love Speed 2024]
tammyeverts
7
570
Site-Speed That Sticks
csswizardry
2
270
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
33
2.7k
How to Ace a Technical Interview
jacobian
276
23k
The Myth of the Modular Monolith - Day 2 Keynote - Rails World 2024
eileencodes
19
2.3k
Automating Front-end Workflow
addyosmani
1366
200k
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