Upgrade to PRO for Only $50/Year—Limited-Time Offer! 🔥
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
710
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
1k
Explorando la conexión entre test smells y la práctica del TDD - GRIAL - research group
marabesi
0
41
Una introducción a eXtreme Programming
marabesi
0
110
TDD anti patterns - episode 6 - with Ignacio Saporitti and Pablo Díaz
marabesi
0
470
TDD anti patterns - episode 5 - with Sofia Carballo and Juan Pablo
marabesi
0
400
TDD anti patterns - episode 4 - with Javier Martínez
marabesi
0
550
TDD anti patterns - episode 3 - With Juan Pablo
marabesi
0
640
TDD anti patterns - episode 2 - TDD anti patterns - With Giulio Perrone
marabesi
0
730
Tips for improving test assertions at Codurance
marabesi
0
1.2k
Other Decks in Technology
See All in Technology
新 Security HubがついにGA!仕組みや料金を深堀り #AWSreInvent #regrowth / AWS Security Hub Advanced GA
masahirokawahara
1
1.6k
AIと二人三脚で育てた、個人開発アプリグロース術
zozotech
PRO
1
690
AWS Bedrock AgentCoreで作る 1on1支援AIエージェント 〜Memory × Evaluationsによる実践開発〜
yusukeshimizu
6
380
ブロックテーマとこれからの WordPress サイト制作 / Toyama WordPress Meetup Vol.81
torounit
0
530
寫了幾年 Code,然後呢?軟體工程師必須重新認識的 DevOps
cheng_wei_chen
1
1.1k
AI 駆動開発勉強会 フロントエンド支部 #1 w/あずもば
1ftseabass
PRO
0
240
多様なデジタルアイデンティティを攻撃からどうやって守るのか / 20251212
ayokura
0
360
【AWS re:Invent 2025速報】AIビルダー向けアップデートをまとめて解説!
minorun365
4
480
AWS CLIの新しい認証情報設定方法aws loginコマンドの実態
wkm2
6
640
Microsoft Agent 365 を 30 分でなんとなく理解する
skmkzyk
1
1k
非CUDAの悲哀 〜Claude Code と挑んだ image to 3D “Hunyuan3D”を EVO-X2(Ryzen AI Max+395)で動作させるチャレンジ〜
hawkymisc
1
160
Lambdaの常識はどう変わる?!re:Invent 2025 before after
iwatatomoya
1
390
Featured
See All Featured
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
25
1.6k
Measuring & Analyzing Core Web Vitals
bluesmoon
9
700
Large-scale JavaScript Application Architecture
addyosmani
515
110k
A better future with KSS
kneath
240
18k
[SF Ruby Conf 2025] Rails X
palkan
0
500
Building a Scalable Design System with Sketch
lauravandoore
463
34k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
35
2.3k
Java REST API Framework Comparison - PWX 2021
mraible
34
9k
The Straight Up "How To Draw Better" Workshop
denniskardys
239
140k
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
9
1k
Being A Developer After 40
akosma
91
590k
Balancing Empowerment & Direction
lara
5
790
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