The programmer's brain - By Felienne Hermans

Transcript

1. The programmer's
   brain
   By Felienne Hermans
   

   View Slide

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

   View Slide

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

   View Slide

4. 1. The memory
   

   View Slide

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

   View Slide

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

   View Slide

7. SPACED
   REPETITION,
   REVISIT
   

   View Slide

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

   View Slide

9. 2. Reading code
   

   View Slide

10. 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
    

    View Slide

11. 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
    

    View Slide

12. 3. Naming
    

    View Slide

13. 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
    

    View Slide

14. 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
    

    View Slide

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

    View Slide

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

    View Slide

17. 4. Writing code
    

    View Slide

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

    View Slide

19. FlowLight
    Manuela Züger
    

    View Slide

20. https://andre-meyer.ch/flowlight
    

    View Slide

21. https://andre-meyer.ch/flowlight
    

    View Slide

22. https://andre-meyer.ch/flowlight
    

    View Slide

23. 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
    

    View Slide

24. The programmer's
    brain
    By Felienne Hermans
    

    View Slide