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
670
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
990
Explorando la conexión entre test smells y la práctica del TDD - GRIAL - research group
marabesi
0
37
Una introducción a eXtreme Programming
marabesi
0
100
TDD anti patterns - episode 6 - with Ignacio Saporitti and Pablo Díaz
marabesi
0
440
TDD anti patterns - episode 5 - with Sofia Carballo and Juan Pablo
marabesi
0
370
TDD anti patterns - episode 4 - with Javier Martínez
marabesi
0
530
TDD anti patterns - episode 3 - With Juan Pablo
marabesi
0
620
TDD anti patterns - episode 2 - TDD anti patterns - With Giulio Perrone
marabesi
0
700
Tips for improving test assertions at Codurance
marabesi
0
1.2k
Other Decks in Technology
See All in Technology
Exadata Database Service on Dedicated Infrastructure(ExaDB-D) UI スクリーン・キャプチャ集
oracle4engineer
PRO
2
5.5k
データエンジニアがこの先生きのこるには...?
10xinc
0
450
SOC2取得の全体像
shonansurvivors
1
410
業務自動化プラットフォーム Google Agentspace に入門してみる #devio2025
maroon1st
0
200
リーダーになったら未来を語れるようになろう/Speak the Future
sanogemaru
0
300
JAZUG 15周年記念 × JAT「AI Agent開発者必見:"今"のOracle技術で拡張するAzure × OCIの共存アーキテクチャ」
shisyu_gaku
0
130
extension 現場で使えるXcodeショートカット一覧
ktombow
0
220
実装で解き明かす並行処理の歴史
zozotech
PRO
1
540
"プロポーザルってなんか怖そう"という境界を超えてみた@TSUDOI by giftee Tech #1
shilo113
0
120
空間を設計する力を考える / 20251004 Naoki Takahashi
shift_evolve
PRO
3
410
M5製品で作るポン置きセルラー対応カメラ
sayacom
0
160
OCI Network Firewall 概要
oracle4engineer
PRO
1
7.8k
Featured
See All Featured
The Myth of the Modular Monolith - Day 2 Keynote - Rails World 2024
eileencodes
26
3.1k
Fantastic passwords and where to find them - at NoRuKo
philnash
52
3.4k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
333
22k
Writing Fast Ruby
sferik
629
62k
What’s in a name? Adding method to the madness
productmarketing
PRO
23
3.7k
Balancing Empowerment & Direction
lara
4
680
Agile that works and the tools we love
rasmusluckow
331
21k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
358
30k
Gamification - CAS2011
davidbonilla
81
5.5k
Code Review Best Practice
trishagee
72
19k
How to Create Impact in a Changing Tech Landscape [PerfNow 2023]
tammyeverts
54
3k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
PRO
23
1.5k
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