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
900
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
42
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
580
TDD anti patterns - episode 5 - with Sofia Carballo and Juan Pablo
marabesi
0
560
TDD anti patterns - episode 4 - with Javier Martínez
marabesi
0
650
TDD anti patterns - episode 3 - With Juan Pablo
marabesi
0
720
TDD anti patterns - episode 2 - TDD anti patterns - With Giulio Perrone
marabesi
0
870
Other Decks in Technology
See All in Technology
SoccerMaster: A Vision Foundation Model for Soccer Understanding
kzykmyzw
0
150
AIコード生成×サプライチェーン攻撃 — PHPが直面する“二重の信頼問題
shinyasaita
0
240
[2026-07-15] AI Ready なはずだったアーキテクチャと、見えてきた課題・次に目指す状態
wxyzzz
11
4k
そのドキュメント、自動化しませんか?
yuksew
1
330
タスクの複雑さでモデルを選ぶ ── Thompson Samplingで動かす“トークン/コスト最適化
satohy0323
0
580
凡エンジニアがこの先生きのこるためには。〜TypeScript完全に理解したい〜
alchemy1115
2
320
2年前に削除したPHPクラスが、 ある日突然決済をエラーにした
ykagano
1
520
Genie Ontologyは銀の弾丸かを考える / Is Genie Ontology a Silver Bullet?
nttcom
0
420
Playwright × AI Agent でE2Eテストはどう変わるか AI駆動テストの可能性と実用検証の結果
taiga7543
1
570
Network Firewallやっていき!
news_it_enj
0
170
AI時代のYAGNI:「爆速で無駄になった機能」からの学び / 20260720 Naoki Takahashi
shift_evolve
PRO
3
410
AIレビューはどこまで任せられるのか?自動化と人が背負うレビューの境界
sansantech
PRO
3
1.1k
Featured
See All Featured
Context Engineering - Making Every Token Count
addyosmani
9
1k
A Tale of Four Properties
chriscoyier
163
24k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
287
14k
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
sstephenson
162
16k
GraphQLとの向き合い方2022年版
quramy
50
15k
The Power of CSS Pseudo Elements
geoffreycrofte
82
6.4k
How to build a perfect <img>
jonoalderson
1
5.8k
Become a Pro
speakerdeck
PRO
31
6k
<Decoding/> the Language of Devs - We Love SEO 2024
nikkihalliwell
1
280
Un-Boring Meetings
codingconduct
0
350
Introduction to Domain-Driven Design and Collaborative software design
baasie
1
900
Principles of Awesome APIs and How to Build Them.
keavy
128
18k
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