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
500
The programmer's brain - By Felienne Hermans
Marabesi
January 21, 2022
Tweet
Share
More Decks by Marabesi
See All by Marabesi
Explorando un modelo de maturidad para un desarrollo guiado por tests - GRIAL - research group
marabesi
0
7
Una introducción a eXtreme Programming
marabesi
0
19
TDD anti patterns - episode 6 - with Ignacio Saporitti and Pablo Díaz
marabesi
0
310
TDD anti patterns - episode 5 - with Sofia Carballo and Juan Pablo
marabesi
0
270
TDD anti patterns - episode 4 - with Javier Martínez
marabesi
0
400
TDD anti patterns - episode 3 - With Juan Pablo
marabesi
0
460
TDD anti patterns - episode 2 - TDD anti patterns - With Giulio Perrone
marabesi
0
510
Tips for improving test assertions at Codurance
marabesi
0
960
TDD anti-patterns at Codurance Spain
marabesi
0
1.7k
Other Decks in Technology
See All in Technology
ペパボのオブザーバビリティ研修2024 説明資料
kesompochy
0
1.1k
20240725 LLMによるDXのビジョンと、今何からやるべきか @Azure OpenAI Service Dev Day
nrryuya
3
1.2k
What if...? 처음부터 다시 LLM 어플리케이션을 개발한다면
huffon
0
1k
CEL(Common Expression Language)で書いた条件にマッチしたIAM Policyを見つける / iam-policy-finder
fujiwara3
0
710
[NIKKEI Tech Talk]Bias for Action!! 実践から学ぶための仕組とコミュニティ / Community for Practice and Learning
kanamasa
0
280
LINE WORKSへ簡単通知!Incoming Webhookアプリの紹介
mmclsntr
0
110
20240724_cm_odyssey_hibiyatech
hiashisan
0
110
ABEMAにおけるLLMを用いたコンテンツベース推薦システム導入と効果検証
cyberagentdevelopers
PRO
1
750
【基調講演】変える、今ここから ― IoTとAIで紡ぐ未来
soracom
PRO
0
320
開発生産性をむしろ向上させる セキュリティパートナーの作り方 / Dev Productivity Con 2024
flatt_security
0
380
「単なる OAuth 2.0 を認証に使うと、車が通れるほどのどでかいセキュリティー・ホールができる」のか検証してみた
terara
0
380
DDDにおける認可の扱いとKotlinにおける実装パターン / authorization-for-ddd-and-kotlin-implement-pattern
urmot
4
390
Featured
See All Featured
We Have a Design System, Now What?
morganepeng
46
7k
Reflections from 52 weeks, 52 projects
jeffersonlam
346
19k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
228
16k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
129
32k
Building Effective Engineering Teams - LeadDev
addyosmani
47
2.2k
The Power of CSS Pseudo Elements
geoffreycrofte
64
5.2k
Designing the Hi-DPI Web
ddemaree
276
34k
Building Flexible Design Systems
yeseniaperezcruz
323
37k
Done Done
chrislema
179
15k
Embracing the Ebb and Flow
colly
81
4.3k
Making Projects Easy
brettharned
111
5.7k
What the flash - Photography Introduction
edds
65
11k
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