Upgrade to Pro — share decks privately, control downloads, hide ads and more …

The programmer's brain - By Felienne Hermans

Marabesi
January 21, 2022

The programmer's brain - By Felienne Hermans

Marabesi

January 21, 2022
Tweet

More Decks by Marabesi

Other Decks in Technology

Transcript

  1. The programmer's
    brain
    By Felienne Hermans

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  4. 1. The memory

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  7. SPACED
    REPETITION,
    REVISIT

    View full-size slide

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

    View full-size slide

  9. 2. Reading code

    View full-size 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 full-size 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 full-size slide

  12. 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 full-size 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
    * Linking chuks

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  16. 4. Writing code

    View full-size slide

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

    View full-size slide

  18. FlowLight
    Manuela Züger

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  22. 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 full-size slide

  23. The programmer's
    brain
    By Felienne Hermans

    View full-size slide