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
0
740
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
120
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
410
TDD anti patterns - episode 4 - with Javier Martínez
marabesi
0
560
TDD anti patterns - episode 3 - With Juan Pablo
marabesi
0
640
TDD anti patterns - episode 2 - TDD anti patterns - With Giulio Perrone
marabesi
0
750
Tips for improving test assertions at Codurance
marabesi
0
1.3k
Other Decks in Technology
See All in Technology
Qiita Bash アドカレ LT #1
okaru
0
170
Master Dataグループ紹介資料
sansan33
PRO
1
4.2k
スクラムマスターが スクラムチームに入って取り組む5つのこと - スクラムガイドには書いてないけど入った当初から取り組んでおきたい大切なこと -
scrummasudar
1
1.5k
ハッカソンから社内プロダクトへ AIエージェント ko☆shi 開発で学んだ4つの重要要素
leveragestech
0
560
純粋なイミュータブルモデルを設計してからイベントソーシングと組み合わせるDeciderの実践方法の紹介 /Introducing Decider Pattern with Event Sourcing
tomohisa
1
670
Keynoteから見るAWSの頭の中
nrinetcom
PRO
1
160
名刺メーカーDevグループ 紹介資料
sansan33
PRO
0
1k
Authlete で実装する MCP OAuth 認可サーバー #CIMD の実装を添えて
watahani
0
420
AWS re:Inventre:cap ~AmazonNova 2 Omniのワークショップを体験してきた~
nrinetcom
PRO
0
130
ECS_EKS以外の選択肢_ROSA入門_.pdf
masakiokuda
1
120
Scrum Guide Expansion Pack が示す現代プロダクト開発への補完的視点
sonjin
0
420
re:Invent2025 セッションレポ ~Spec-driven development with Kiro~
nrinetcom
PRO
2
170
Featured
See All Featured
StorybookのUI Testing Handbookを読んだ
zakiyama
31
6.5k
[RailsConf 2023] Rails as a piece of cake
palkan
58
6.2k
SEO Brein meetup: CTRL+C is not how to scale international SEO
lindahogenes
0
2.3k
Marketing to machines
jonoalderson
1
4.5k
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
49
3.3k
The Curious Case for Waylosing
cassininazir
0
200
Google's AI Overviews - The New Search
badams
0
890
Bioeconomy Workshop: Dr. Julius Ecuru, Opportunities for a Bioeconomy in West Africa
akademiya2063
PRO
0
37
GraphQLの誤解/rethinking-graphql
sonatard
74
11k
Have SEOs Ruined the Internet? - User Awareness of SEO in 2025
akashhashmi
0
230
RailsConf 2023
tenderlove
30
1.3k
Avoiding the “Bad Training, Faster” Trap in the Age of AI
tmiket
0
45
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