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
Sponsored
·
Your Podcast. Everywhere. Effortlessly.
Share. Educate. Inspire. Entertain. You do you. We'll handle the rest.
→
Marabesi
January 21, 2022
Technology
830
0
Share
The programmer's brain - By Felienne Hermans
Marabesi
January 21, 2022
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
51
Una introducción a eXtreme Programming
marabesi
0
140
TDD anti patterns - episode 6 - with Ignacio Saporitti and Pablo Díaz
marabesi
0
530
TDD anti patterns - episode 5 - with Sofia Carballo and Juan Pablo
marabesi
0
510
TDD anti patterns - episode 4 - with Javier Martínez
marabesi
0
610
TDD anti patterns - episode 3 - With Juan Pablo
marabesi
0
690
TDD anti patterns - episode 2 - TDD anti patterns - With Giulio Perrone
marabesi
0
840
Tips for improving test assertions at Codurance
marabesi
0
1.3k
Other Decks in Technology
See All in Technology
AI対話分析の夢と、汚いデータの現実 Looker / Dataplex / Dataform で実現する品質ファーストな基盤設計
waiwai2111
0
520
クラウドネイティブ DB はいかにして制約を 克服したか? 〜進化歴史から紐解く、スケーラブルアーキテクチャ設計指針〜
hacomono
PRO
6
1k
小さいVue.jsを30分で作る
hal_spidernight
0
160
AIの揺らぎに“コシ”を与える階層化品質設計
ickx
0
280
R&D 祭 2024 UE5で絵コンテ・作画の制作支援ツールをつくる話
olmdrd
PRO
0
140
How to learn AWS Well-Architected with AWS BuilderCards: Security Edition
coosuke
PRO
0
140
20260515 OpenIDファウンデーション・ジャパンご紹介
oidfj
0
110
エンタープライズの厳格な制約を開発者に意識させない:クラウドネイティブ開発基盤設計/cloudnative-kaigi-golden-path
mhrtech
0
430
セキュリティ対策、何からはじめる? CloudNative環境の脅威モデリングと リスク評価実践入門 #cloudnativekaigi
varu3
5
920
Claude Code / Codex / Kiro に AWS 権限を 渡すとき、何を設計すべきか
k_adachi_01
5
1.4k
SREの仕事は「壊さないこと」ではなくなった 〜自律化していくシステムに、責任と判断を与えるという価値〜 / 20260515 Naoki Shimada
shift_evolve
PRO
1
160
AI飲み会幹事エージェントを作っただけなのに
ykimi
0
210
Featured
See All Featured
"I'm Feeling Lucky" - Building Great Search Experiences for Today's Users (#IAC19)
danielanewman
231
23k
The browser strikes back
jonoalderson
0
1k
Balancing Empowerment & Direction
lara
6
1.1k
Principles of Awesome APIs and How to Build Them.
keavy
128
17k
Technical Leadership for Architectural Decision Making
baasie
3
360
Put a Button on it: Removing Barriers to Going Fast.
kastner
60
4.3k
SEO Brein meetup: CTRL+C is not how to scale international SEO
lindahogenes
1
2.6k
Joys of Absence: A Defence of Solitary Play
codingconduct
1
360
The Illustrated Guide to Node.js - THAT Conference 2024
reverentgeek
1
350
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
25
1.9k
Ecommerce SEO: The Keys for Success Now & Beyond - #SERPConf2024
aleyda
1
2k
Are puppies a ranking factor?
jonoalderson
1
3.4k
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