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
880
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
CISTI 2026 - Test-Driven Development Versus Test Smells: An Empirical Study With Students From UFABC University
marabesi
0
27
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
57
Una introducción a eXtreme Programming
marabesi
0
160
TDD anti patterns - episode 6 - with Ignacio Saporitti and Pablo Díaz
marabesi
0
560
TDD anti patterns - episode 5 - with Sofia Carballo and Juan Pablo
marabesi
0
550
TDD anti patterns - episode 4 - with Javier Martínez
marabesi
0
630
TDD anti patterns - episode 3 - With Juan Pablo
marabesi
0
700
TDD anti patterns - episode 2 - TDD anti patterns - With Giulio Perrone
marabesi
0
860
Other Decks in Technology
See All in Technology
10年間のブログ発信を振り返って見えたWebアプリケーションエンジニアとしての軌跡
stefafafan
0
180
あなたの知らないPDFのアクセシビリティ
lycorptech_jp
PRO
0
240
感情と身体を置き去りにしない、エンジニアの生きのこり方 ──いまから、ここから「自分の状態」を扱うという選択
saorimurooka
0
320
SONiCの統計情報を取得したい
sonic
0
300
脱SaaS!FDEを支えるプロビジョニングと分離設計
knih
0
260
When Platform Engineering Meets GenAI
sucitw
0
170
作る力から、見極める力へ — AI時代に広がるエンジニアの価値と役割
rince
0
320
5分でわかるDuckDB Quack
chanyou0311
2
240
クレデンシャル流出 ― 攻撃 3 時間 vs 復旧 10 時間。この非対称性にどう備えるか
kazzpapa3
3
540
技術・能力を向上する原理原則 #きのこセッションa #きのこ2026
bash0c7
0
110
螺旋型キャリアの生存戦略 / kinoko-conf2026
rakus_dev
1
900
Deep Data Security 機能解説
oracle4engineer
PRO
2
110
Featured
See All Featured
The Spectacular Lies of Maps
axbom
PRO
1
820
The Pragmatic Product Professional
lauravandoore
37
7.3k
Prompt Engineering for Job Search
mfonobong
0
350
Joys of Absence: A Defence of Solitary Play
codingconduct
1
400
A brief & incomplete history of UX Design for the World Wide Web: 1989–2019
jct
2
400
Learning to Love Humans: Emotional Interface Design
aarron
275
41k
State of Search Keynote: SEO is Dead Long Live SEO
ryanjones
0
210
XXLCSS - How to scale CSS and keep your sanity
sugarenia
250
1.3M
Building Adaptive Systems
keathley
44
3.1k
How To Speak Unicorn (iThemes Webinar)
marktimemedia
1
490
WENDY [Excerpt]
tessaabrams
11
38k
I Don’t Have Time: Getting Over the Fear to Launch Your Podcast
jcasabona
34
2.8k
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