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
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
410
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
750
Tips for improving test assertions at Codurance
marabesi
0
1.3k
Other Decks in Technology
See All in Technology
2025年の医用画像AI/AI×medical_imaging_in_2025_generated_by_AI
tdys13
0
260
[Neurogica] 採用ポジション/ Recruitment Position
neurogica
1
140
AWS re:Invent2025最新動向まとめ(NRIグループre:Cap 2025)
gamogamo
0
140
Oracle Database@Google Cloud:サービス概要のご紹介
oracle4engineer
PRO
1
810
「もしもデータ基盤開発で『強くてニューゲーム』ができたなら今の僕はどんなデータ基盤を作っただろう」
aeonpeople
0
270
小さく、早く、可能性を多産する。生成AIプロジェクト / prAIrie-dog
visional_engineering_and_design
0
270
"人"が頑張るAI駆動開発
yokomachi
1
670
Entity Framework Core におけるIN句クエリ最適化について
htkym
0
140
ESXi のAIOps だ!2025冬
unnowataru
0
450
人工知能のための哲学塾 ニューロフィロソフィ篇 第零夜 「ニューロフィロソフィとは何か?」
miyayou
0
220
TED_modeki_共創ラボ_20251203.pdf
iotcomjpadmin
0
190
普段使ってるClaude Skillsの紹介(by Notebooklm)
zerebom
8
2.6k
Featured
See All Featured
Mozcon NYC 2025: Stop Losing SEO Traffic
samtorres
0
100
The innovator’s Mindset - Leading Through an Era of Exponential Change - McGill University 2025
jdejongh
PRO
1
74
Leveraging LLMs for student feedback in introductory data science courses - posit::conf(2025)
minecr
0
97
Statistics for Hackers
jakevdp
799
230k
Automating Front-end Workflow
addyosmani
1371
200k
Building Flexible Design Systems
yeseniaperezcruz
330
39k
How to make the Groovebox
asonas
2
1.9k
What Being in a Rock Band Can Teach Us About Real World SEO
427marketing
0
150
Docker and Python
trallard
47
3.7k
Designing for Timeless Needs
cassininazir
0
110
The Power of CSS Pseudo Elements
geoffreycrofte
80
6.1k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
35
2.3k
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