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
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
20260515 ログイン機能だけではないアカウント管理を全体で考える~サービス設計者向け~
oidfj
0
300
O'Reilly Infrastructure & Ops Superstream: Platform Engineering for Developers, Architects & the Rest of Us
syntasso
0
110
変化の激しい時代をゴキゲンに生き抜くために 〜ストレスマネジメントのススメ〜
kakehashi
PRO
5
1.3k
Purview Endpoint DLP 動かしてみた
kozakigh
0
390
Sociotechnical Architecture Reviews: Understanding Teams, not just Artefacts
ewolff
1
170
全社統制を維持しながら現場負担をどう減らすか〜プラットフォームチームとセキュリティチームで進めたSecurity Hub活用によるAWS統制の見直し〜/secjaws-security-hub-custom-insights
mhrtech
1
480
freeeで運用しているAIQAについて
qatonchan
1
580
Purview 勉強会報告 Microsoft Purview 入門しようとしてみた
masakichixo
1
390
SLI/SLO、「完全に理解した」から「チョットデキル」へ
maruloop
5
470
可視化から活用へ — Mesh化・Segmentation・アライメントの研究動向
gpuunite_official
0
190
Oracle AI Database@AWS:サービス概要のご紹介
oracle4engineer
PRO
4
2.5k
「強制アップデート」か「チームの自律」か?エンタープライズが辿り着いたプラットフォームのハイブリッド運用/cloudnative-kaigi-hybrid-platform-operations
mhrtech
0
200
Featured
See All Featured
Test your architecture with Archunit
thirion
1
2.2k
Organizational Design Perspectives: An Ontology of Organizational Design Elements
kimpetersen
PRO
1
690
Rebuilding a faster, lazier Slack
samanthasiow
85
9.5k
Have SEOs Ruined the Internet? - User Awareness of SEO in 2025
akashhashmi
0
340
A Soul's Torment
seathinner
6
2.8k
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
10
1.2k
Everyday Curiosity
cassininazir
0
200
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
sstephenson
162
16k
Chasing Engaging Ingredients in Design
codingconduct
0
190
Music & Morning Musume
bryan
47
7.2k
Evolving SEO for Evolving Search Engines
ryanjones
0
190
Navigating Algorithm Shifts & AI Overviews - #SMXNext
aleyda
1
1.2k
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