Slide 1

Slide 1 text

The programmer's brain By Felienne Hermans

Slide 2

Slide 2 text

Hello there - This is a book is the intersection between learning and tech.

Slide 3

Slide 3 text

Agenda What's the idea: Go over the following sections: 1. The memory 2. Reading code 3. Writing code 4. Naming

Slide 4

Slide 4 text

1. The memory

Slide 5

Slide 5 text

Memory classification - Working memory - Short term memory - Long term memory

Slide 6

Slide 6 text

Memory classification - Working memory - Short term memory - Long term memory * The magical number seven minus or plus two

Slide 7

Slide 7 text

SPACED REPETITION, REVISIT

Slide 8

Slide 8 text

Cognitive refactoring - Grab a piece of code - Place that where you need - Remove that afterwards

Slide 9

Slide 9 text

2. Reading code

Slide 10

Slide 10 text

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

Slide 11

Slide 11 text

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

Slide 12

Slide 12 text

3. Naming

Slide 13

Slide 13 text

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

Slide 14

Slide 14 text

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

Slide 15

Slide 15 text

W.M → L.T.M L.T.M → W.M

Slide 16

Slide 16 text

Naming she refers a research that points to 19% increase on finding defects for code that does is not abbreviated.

Slide 17

Slide 17 text

4. Writing code

Slide 18

Slide 18 text

Writing - an interrupted task takes longer to finish compared to a uninterrupted on, this is what research points to.

Slide 19

Slide 19 text

FlowLight Manuela Züger

Slide 20

Slide 20 text

https://andre-meyer.ch/flowlight

Slide 21

Slide 21 text

https://andre-meyer.ch/flowlight

Slide 22

Slide 22 text

https://andre-meyer.ch/flowlight

Slide 23

Slide 23 text

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

Slide 24

Slide 24 text

The programmer's brain By Felienne Hermans