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
930
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
The programmer's brain - By Felienne Hermans
Marabesi
January 21, 2022
More Decks by Marabesi
See All by Marabesi
Software Metrics Machine
marabesi
0
25
CISTI 2026 - Test-Driven Development Versus Test Smells: An Empirical Study With Students From UFABC University
marabesi
0
43
A comprehensive view of refactoring
marabesi
0
1.2k
Explorando la conexión entre test smells y la práctica del TDD - GRIAL - research group
marabesi
0
63
Una introducción a eXtreme Programming
marabesi
0
170
TDD anti patterns - episode 6 - with Ignacio Saporitti and Pablo Díaz
marabesi
0
580
TDD anti patterns - episode 5 - with Sofia Carballo and Juan Pablo
marabesi
0
580
TDD anti patterns - episode 4 - with Javier Martínez
marabesi
0
670
TDD anti patterns - episode 3 - With Juan Pablo
marabesi
0
730
Other Decks in Technology
See All in Technology
攻撃と防御で学ぶAI時代のプロダクトセキュリティ演習
recruitengineers
PRO
9
2.8k
モダンフロントエンド 開発研修
recruitengineers
PRO
4
630
社内の7割が使うデータ基盤を、 データチーム2人で回すためにやったこと
koh_yoshi
4
1.3k
侵入は突然に 〜 IoTマルウェアと悪用される家庭の機器 ~ / When Intrusion Strikes: IoT Malware and the Abuse of Home Devices
nttcom
0
1.6k
名刺メーカーDevグループ 紹介資料
sansan33
PRO
0
1.2k
オートロックマンションなのに、各部屋は施錠なし!? 攻撃者が組織内ネットワークで大暴れする理由 / The Front Door Is Locked, but the Rooms Are Wide Open: Why Attackers Move Freely Inside Enterprise Networks
nttcom
1
1.7k
Bill One 開発エンジニア 紹介資料
sansan33
PRO
7
19k
Contract One Engineering Unit 紹介資料
sansan33
PRO
0
19k
Master Dataグループ紹介資料
sansan33
PRO
1
4.8k
【CEDEC2026】『Relink』を拡張せよ - 『GRANBLUE FANTASY: Relink - Endless Ragnarok』の開発速度と品質を守るCI運用
cygames
PRO
0
170
TypeScript入門 2026
recruitengineers
PRO
3
570
取引先から届く 「セキュリティチェックシート」の読み解き方
kamadamakoto
0
150
Featured
See All Featured
Building AI with AI
inesmontani
PRO
1
1.1k
The AI Search Optimization Roadmap by Aleyda Solis
aleyda
1
6.1k
RailsConf 2023
tenderlove
30
1.5k
It's Worth the Effort
3n
188
29k
Why You Should Never Use an ORM
jnunemaker
PRO
61
10k
Navigating Weather and Climate Data
rabernat
0
470
Build The Right Thing And Hit Your Dates
maggiecrowley
39
3.4k
Intergalactic Javascript Robots from Outer Space
tanoku
273
27k
Why Your Marketing Sucks and What You Can Do About It - Sophie Logan
marketingsoph
0
380
The Curious Case for Waylosing
cassininazir
1
450
Leading Effective Engineering Teams in the AI Era
addyosmani
9
2.3k
Embracing the Ebb and Flow
colly
88
5.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