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
Sponsored
·
SiteGround - Reliable hosting with speed, security, and support you can count on.
→
Marabesi
January 21, 2022
Technology
850
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
53
Una introducción a eXtreme Programming
marabesi
0
150
TDD anti patterns - episode 6 - with Ignacio Saporitti and Pablo Díaz
marabesi
0
540
TDD anti patterns - episode 5 - with Sofia Carballo and Juan Pablo
marabesi
0
530
TDD anti patterns - episode 4 - with Javier Martínez
marabesi
0
610
TDD anti patterns - episode 3 - With Juan Pablo
marabesi
0
690
TDD anti patterns - episode 2 - TDD anti patterns - With Giulio Perrone
marabesi
0
840
Tips for improving test assertions at Codurance
marabesi
0
1.3k
Other Decks in Technology
See All in Technology
Strands Agents超入門
kintotechdev
1
120
オンコールの負荷軽減のためのBits Assistant 活用方法 / How to Use Bits Assistant to Reduce the Workload on On-Call Staff
sms_tech
1
200
Spring AI × MCP 入門〜AIエージェントへのツール公開、境界設計から始める最小構成 〜
yuyamiyamoto
0
110
個人AIからチームAIへ:開発における品質と生産性の再設計
moongift
PRO
0
210
最低限これだけ押さえれ大丈夫_Claude Enterprise/Team企業展開ガバナンス入門
tkikuchi
1
260
TypeScript で Platform SDK を作る技術
toiroakr
1
320
eBPF Can Do It! A 5-Minute Tour of 5 Real-World PHP Issues Solved with eBPF
egmc
0
290
AI とサービス・デザイン / AI and Service Design
ks91
PRO
0
180
TROCCOで始めるクラウドコストを民主化するためのFinOps
tk3fftk
1
230
大規模環境でどのように監視を実現する?
yuobayashi
1
150
実践 TanStack Start ― 新規プロダクトを開発して確立した、サーバーとクライアント境界の設計パターン / Practical TanStack Start Server-Client Boundary Patterns
kaminashi
2
330
AI駆動開発でなんでもハンズオン環境をつくってみた
yoshimi0227
0
160
Featured
See All Featured
Building the Perfect Custom Keyboard
takai
2
770
30 Presentation Tips
portentint
PRO
1
300
Side Projects
sachag
455
43k
No one is an island. Learnings from fostering a developers community.
thoeni
21
3.7k
End of SEO as We Know It (SMX Advanced Version)
ipullrank
3
4.2k
Game over? The fight for quality and originality in the time of robots
wayneb77
1
180
Designing Experiences People Love
moore
143
24k
VelocityConf: Rendering Performance Case Studies
addyosmani
333
25k
For a Future-Friendly Web
brad_frost
183
10k
Reflections from 52 weeks, 52 projects
jeffersonlam
356
21k
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
659
62k
Deep Space Network (abreviated)
tonyrice
0
150
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