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
810
0
Share
The programmer's brain - By Felienne Hermans
Marabesi
January 21, 2022
More Decks by Marabesi
See All by Marabesi
A comprehensive view of refactoring
marabesi
0
1.1k
Explorando la conexión entre test smells y la práctica del TDD - GRIAL - research group
marabesi
0
50
Una introducción a eXtreme Programming
marabesi
0
140
TDD anti patterns - episode 6 - with Ignacio Saporitti and Pablo Díaz
marabesi
0
520
TDD anti patterns - episode 5 - with Sofia Carballo and Juan Pablo
marabesi
0
480
TDD anti patterns - episode 4 - with Javier Martínez
marabesi
0
600
TDD anti patterns - episode 3 - With Juan Pablo
marabesi
0
680
TDD anti patterns - episode 2 - TDD anti patterns - With Giulio Perrone
marabesi
0
830
Tips for improving test assertions at Codurance
marabesi
0
1.3k
Other Decks in Technology
See All in Technology
マルチプロダクトの信頼性を効率良く保っていくために
kworkdev
PRO
0
160
20260428_Product Management Summit_tadokoroyoshiro
tadokoro_yoshiro
2
890
20年前の「OSS革命」に学ぶ AI時代の生存戦略
samakada
0
440
コードや知識を組み込む / Incorporate Code and Knowledge
ks91
PRO
0
160
QGISプラグイン CMChangeDetector
naokimuroki
1
410
小説執筆のハーネスエンジニアリング
yoshitetsu
0
720
国内外の生成AIセキュリティの最新動向 & AIガードレール製品「chakoshi」のご紹介 / Latest Trends in Generative AI Security (Domestic & International) & Introduction to AI Guardrail Product "chakoshi"
nttcom
3
1.2k
生成AIが変える SaaS の競争原理と弁護士ドットコムのプロダクト戦略
bengo4com
1
1k
扱える不確実性を増やしていく - スタートアップEMが考える「任せ方」
kadoppe
0
310
AWS DevOps Agentはチームメイトになれるのか?/ Can AWS DevOps Agent become a teammate
kinunori
6
750
最近の技術系の話題で気になったもの色々(IoT系以外も) / IoTLT 花見予定会(たぶんBBQ) @都立潮風公園バーベキュー広場
you
PRO
1
240
エージェントスキルを作って自分のインプットに役立てよう
tsubakimoto_s
0
380
Featured
See All Featured
Side Projects
sachag
455
43k
Rebuilding a faster, lazier Slack
samanthasiow
85
9.5k
Done Done
chrislema
186
16k
The Pragmatic Product Professional
lauravandoore
37
7.2k
[SF Ruby Conf 2025] Rails X
palkan
2
960
Joys of Absence: A Defence of Solitary Play
codingconduct
1
350
ラッコキーワード サービス紹介資料
rakko
1
3.1M
Lessons Learnt from Crawling 1000+ Websites
charlesmeaden
PRO
1
1.2k
The Art of Delivering Value - GDevCon NA Keynote
reverentgeek
16
1.9k
Building Flexible Design Systems
yeseniaperezcruz
330
40k
Beyond borders and beyond the search box: How to win the global "messy middle" with AI-driven SEO
davidcarrasco
3
110
A designer walks into a library…
pauljervisheath
211
24k
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