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
760
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
1.1k
Explorando la conexión entre test smells y la práctica del TDD - GRIAL - research group
marabesi
0
48
Una introducción a eXtreme Programming
marabesi
0
130
TDD anti patterns - episode 6 - with Ignacio Saporitti and Pablo Díaz
marabesi
0
490
TDD anti patterns - episode 5 - with Sofia Carballo and Juan Pablo
marabesi
0
430
TDD anti patterns - episode 4 - with Javier Martínez
marabesi
0
570
TDD anti patterns - episode 3 - With Juan Pablo
marabesi
0
650
TDD anti patterns - episode 2 - TDD anti patterns - With Giulio Perrone
marabesi
0
780
Tips for improving test assertions at Codurance
marabesi
0
1.3k
Other Decks in Technology
See All in Technology
自動テストが巻き起こした開発プロセス・チームの変化 / Impact of Automated Testing on Development Cycles and Team Dynamics
codmoninc
0
810
「使いにくい」も「運用疲れ」も卒業する UIデザイナーとエンジニアが創る持続可能な内製開発
nrinetcom
PRO
1
770
JAWS DAYS 2026 CDP道場 事前説明会 / JAWS DAYS 2026 CDP Dojo briefing document
naospon
0
110
OSSで構築するIT基盤管理実践事例: NetBox・Snipe-IT・FreeRADIUS+PrivacyIDEA / Practical Case Studies of IT Infrastructure Management Using OSS
nttcom
0
140
AIに視覚を与えモバイルアプリケーション開発をより円滑に行う
lycorptech_jp
PRO
1
760
社内ワークショップで終わらせない 業務改善AIエージェント開発
lycorptech_jp
PRO
1
440
AI Agentにおける評価指標とAgent GPA
tsho
1
270
Claude Cowork Plugins を読む - Skills駆動型業務エージェント設計の実像と構造
knishioka
0
230
競争優位を生み出す戦略的内製開発の実践技法
masuda220
PRO
2
530
作るべきものと向き合う - ecspresso 8年間の開発史から学ぶ技術選定 / 技術選定con findy 2026
fujiwara3
6
1.7k
マルチロールEMが実践する「組織のレジリエンス」を高めるための組織構造と人材配置戦略
coconala_engineer
2
130
マネージャー版 "提案のレベル" を上げる
konifar
10
4.5k
Featured
See All Featured
No one is an island. Learnings from fostering a developers community.
thoeni
21
3.6k
YesSQL, Process and Tooling at Scale
rocio
174
15k
The Limits of Empathy - UXLibs8
cassininazir
1
240
Mind Mapping
helmedeiros
PRO
1
110
Making the Leap to Tech Lead
cromwellryan
135
9.7k
Amusing Abliteration
ianozsvald
0
120
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
333
22k
How to Grow Your eCommerce with AI & Automation
katarinadahlin
PRO
1
130
Being A Developer After 40
akosma
91
590k
The B2B funnel & how to create a winning content strategy
katarinadahlin
PRO
1
290
Bridging the Design Gap: How Collaborative Modelling removes blockers to flow between stakeholders and teams @FastFlow conf
baasie
0
470
Mobile First: as difficult as doing things right
swwweet
225
10k
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