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
760
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
1.1k
Explorando la conexión entre test smells y la práctica del TDD - GRIAL - research group
marabesi
0
48
Una introducción a eXtreme Programming
marabesi
0
130
TDD anti patterns - episode 6 - with Ignacio Saporitti and Pablo Díaz
marabesi
0
490
TDD anti patterns - episode 5 - with Sofia Carballo and Juan Pablo
marabesi
0
430
TDD anti patterns - episode 4 - with Javier Martínez
marabesi
0
570
TDD anti patterns - episode 3 - With Juan Pablo
marabesi
0
650
TDD anti patterns - episode 2 - TDD anti patterns - With Giulio Perrone
marabesi
0
780
Tips for improving test assertions at Codurance
marabesi
0
1.3k
Other Decks in Technology
See All in Technology
Serverless Agent Architecture on Azure / serverless-agent-on-azure
miyake
1
120
社内でAWS BuilderCards体験会を立ち上げ、得られた気づき / 20260225 Masaki Okuda
shift_evolve
PRO
1
150
AI が Approve する開発フロー / How AI Reviewers Accelerate Our Development
zaimy
1
260
Oracle Base Database Service 技術詳細
oracle4engineer
PRO
15
95k
オンプレとGoogle Cloudを安全に繋ぐための、セキュア通信の勘所
waiwai2111
3
1.1k
研究開発部メンバーの働き⽅ / Sansan R&D Profile
sansan33
PRO
4
22k
Contract One Engineering Unit 紹介資料
sansan33
PRO
0
14k
脱・コピペ!自分で調べて書くK8sマニフェスト
devops_vtj
0
110
Claude Codeと駆け抜ける 情報収集と実践録
sontixyou
2
1.3k
LINEアプリ開発のための Claude Code活用基盤の構築
lycorptech_jp
PRO
1
1.3k
ヘルシーSRE
tk3fftk
2
220
競争優位を生み出す戦略的内製開発の実践技法
masuda220
PRO
2
530
Featured
See All Featured
Being A Developer After 40
akosma
91
590k
How to Align SEO within the Product Triangle To Get Buy-In & Support - #RIMC
aleyda
1
1.4k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
234
17k
No one is an island. Learnings from fostering a developers community.
thoeni
21
3.6k
Building AI with AI
inesmontani
PRO
1
760
Why Mistakes Are the Best Teachers: Turning Failure into a Pathway for Growth
auna
0
71
Done Done
chrislema
186
16k
KATA
mclloyd
PRO
35
15k
Measuring Dark Social's Impact On Conversion and Attribution
stephenakadiri
1
140
Gemini Prompt Engineering: Practical Techniques for Tangible AI Outcomes
mfonobong
2
300
Utilizing Notion as your number one productivity tool
mfonobong
4
240
Helping Users Find Their Own Way: Creating Modern Search Experiences
danielanewman
31
3.1k
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