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
生成AI時代の開発組織・技術・プロセス 〜 ログラスの挑戦と考察 〜
itohiro73
1
460
自律的なスケーリング手法FASTにおけるVPoEとしてのアカウンタビリティ / dev-productivity-con-2025
yoshikiiida
1
16k
AI専用のリンターを作る #yumemi_patch
bengo4com
5
4.3k
Sansanのデータプロダクトマネジメントのアプローチ
sansantech
PRO
0
150
American airlines ®️ USA Contact Numbers: Complete 2025 Support Guide
airhelpsupport
0
380
CRE Camp #1 エンジニアリングを民主化するCREチームでありたい話
mntsq
1
120
成長し続けるアプリのためのテストと設計の関係、そして意思決定の記録。
sansantech
PRO
0
120
マーケットプレイス版Oracle WebCenter Content For OCI
oracle4engineer
PRO
3
960
United Airlines Customer Service– Call 1-833-341-3142 Now!
airhelp
0
170
LangChain Interrupt & LangChain Ambassadors meetingレポート
os1ma
2
310
american airlines®️ USA Contact Numbers: Complete 2025 Support Guide
supportflight
1
110
怖くない!はじめてのClaude Code
shinya337
0
390
Featured
See All Featured
How to Ace a Technical Interview
jacobian
278
23k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
331
22k
The Myth of the Modular Monolith - Day 2 Keynote - Rails World 2024
eileencodes
26
2.9k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
34
3.1k
Adopting Sorbet at Scale
ufuk
77
9.5k
Visualization
eitanlees
146
16k
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
656
60k
Building an army of robots
kneath
306
45k
Fantastic passwords and where to find them - at NoRuKo
philnash
51
3.3k
The Pragmatic Product Professional
lauravandoore
35
6.7k
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
507
140k
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
35
2.4k
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