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
750
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
1k
Explorando la conexión entre test smells y la práctica del TDD - GRIAL - research group
marabesi
0
42
Una introducción a eXtreme Programming
marabesi
0
120
TDD anti patterns - episode 6 - with Ignacio Saporitti and Pablo Díaz
marabesi
0
480
TDD anti patterns - episode 5 - with Sofia Carballo and Juan Pablo
marabesi
0
420
TDD anti patterns - episode 4 - with Javier Martínez
marabesi
0
560
TDD anti patterns - episode 3 - With Juan Pablo
marabesi
0
640
TDD anti patterns - episode 2 - TDD anti patterns - With Giulio Perrone
marabesi
0
760
Tips for improving test assertions at Codurance
marabesi
0
1.3k
Other Decks in Technology
See All in Technology
2人で作ったAIダッシュボードが、開発組織の次の一手を照らした話― Cursor × SpecKit × 可視化の実践 ― Qiita AI Summit
noalisaai
1
350
日本語テキストと音楽の対照学習の技術とその応用
lycorptech_jp
PRO
1
410
Kubecon NA 2025: DRA 関連の Recap と社内 GPU 基盤での課題
kevin_namba
0
110
セキュリティ はじめの一歩
nikinusu
0
1.4k
今日から始めるAmazon Bedrock AgentCore
har1101
4
320
変化するコーディングエージェントとの現実的な付き合い方 〜Cursor安定択説と、ツールに依存しない「資産」〜
empitsu
4
1.1k
CDK対応したAWS DevOps Agentを試そう_20260201
masakiokuda
1
130
最速で価値を出すための プロダクトエンジニアのツッコミ術
kaacun
1
520
会社紹介資料 / Sansan Company Profile
sansan33
PRO
15
400k
Sansan Engineering Unit 紹介資料
sansan33
PRO
1
3.8k
茨城の思い出を振り返る ~CDKのセキュリティを添えて~ / 20260201 Mitsutoshi Matsuo
shift_evolve
PRO
1
120
M&A 後の統合をどう進めるか ─ ナレッジワーク × Poetics が実践した組織とシステムの融合
kworkdev
PRO
1
290
Featured
See All Featured
XXLCSS - How to scale CSS and keep your sanity
sugarenia
249
1.3M
Believing is Seeing
oripsolob
1
48
The #1 spot is gone: here's how to win anyway
tamaranovitovic
2
920
Being A Developer After 40
akosma
91
590k
"I'm Feeling Lucky" - Building Great Search Experiences for Today's Users (#IAC19)
danielanewman
231
22k
Faster Mobile Websites
deanohume
310
31k
Bridging the Design Gap: How Collaborative Modelling removes blockers to flow between stakeholders and teams @FastFlow conf
baasie
0
440
Reflections from 52 weeks, 52 projects
jeffersonlam
356
21k
Context Engineering - Making Every Token Count
addyosmani
9
640
The Impact of AI in SEO - AI Overviews June 2024 Edition
aleyda
5
720
[SF Ruby Conf 2025] Rails X
palkan
0
740
Un-Boring Meetings
codingconduct
0
200
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