Reading Code (JFokus)

As developers, we spend a lot of time learning to write code, while spending little to no time learning to read code. Meanwhile, we often spend more time reading code than actually writing it. Shouldn’t we be spending at least the same amount of time and effort improving this skill? Deliberate practice can help us get better at reading code. Learning how to better read and understand code, can in turn teach us what makes code readable. This might even help us to write code that is easier to read.

In this talk we will discuss the benefits of deliberately practicing reading code in a code reading club or session without an IDE, as well as common strategies to navigate a new codebase and familiarise ourselves with the code using the IDE.

Transcript

1. Reading Code JFokus - Feb 6, 2024 https://maritvandijk.com/
2. Reading Code • We spend more time reading code than writing code
3. Reading Code We read code when: • adding features • fi xing bugs • understanding a new system • doing code reviews • learning new technologies • etc.
4. Reading Code "developers on average spend as much as 58% of their time comprehending existing source code" - Felienne Hermans, The Programmer's Brain
5. Reading Code • We spend more time reading code than writing code • But we don't practice reading code explicitly (much)
6. Reading Code "How to teach programming (and other things)?" by Felienne Hermans https://www.youtube.com/watch?v=g1ib43q3uXQ
7. Reading Code • What if we practice reading code explicitly?
8. Code Reading Club • Code Reading Club https://codereading.club/
9. Code Reading Club • Printed code sample • Structured exercises
10. Examples of exercises • First glance • Identify components & relationships • Most important lines • Identify concepts • Summary
11. Code Reading Club Learned about ... • reading code • other peoples' perspectives • noticing my own assumptions
12. Reading Code
13. Reasons code is confusing 1. Lack of knowledge 2. Lack of information 3. Lack of processing power in the brain
14. Lack of knowledge • Programming domain • Language / syntax • Programming constructs / algorithms • Business domain • Domain concepts • Business logic
15. Dealing with a lack of knowledge • Create a list • Research • Memorize
16. Lack of information • Unknown details • Unfamiliar names • Code connected in unknown ways • Too many things at once
17. Dealing with lack of information • Chunking
18. Lack of processing power in the brain • Too many processing steps • Too many variables
19. Dealing with lack of processing power in the brain • Memory aids • Dependency graph • State table
20. Dependency graph
21. State table public class NestedLoop { public static void main(String[] args) { for (int i = 0; i < 2; i++) { System.out.println("i is: " + i); for (int j = 0; j < 2; j++) { System.out.println("j is: " + j); } } } }
22. Dimensions of code reading • Structure • Domain • Concepts • Context
23. Structure Code is not read linearly
24. Domain • Behavior • Data
25. Concepts
26. Context
27. Reading Code The bigger picture
28. Understanding a new code base • Joining a new team / organisation • Using a new code base
29. Reading Code • What does the code do?
30. Context
31. Reading Code A good place to start: • Check out the code
32. Help in the IDE
33. Help in the IDE • Project structure • README • Diagrams • Dependencies • Build & run
34. Strategies • Identify components • Identify relationships / dependencies • Identify concepts • Gain context
35. A slice of the application
36. Find a starting point
37. Find a starting point • Generic • Main method • Endpoint • Speci fi c • Error message / Exception • Logic / Functionality
38. Help in the IDE
39. Help in the IDE • Search • Navigate
40. Strategies • A particular use case • Draw your own diagrams
41. Reading Code Understanding a piece of code
42. Reading Code • Structured exercises
43. Help in the IDE
44. Help in the IDE • Structure • Hints from your IDE • Tests • Refactor for understanding • Context
45. Strategies • Dependency graph • State table • Context for git history
46. Reading Code What's next?
47. Structured exercises • Code Reading Club: https://codereading.club/ • Code Reading Club Resources: https://github.com/CodeReadingClubs/Resources • The Programmer's Brain - Felienne Hermans • Code Reading in Practice - Felienne Hermans & Gien Verschatse (?)
48. Let your tools help you
49. ... and your brain
50. Reading code Slides & More https://maritvandijk.com/presentations/reading-code/
51. Code reading exercise First glance The goal of this exercise is to practice getting a fi rst impression of code. (1 min) Independently - Glance at the code Note down the fi rst thing that catches your eye. Then note the second thing that catches your eye. Think about why you noticed those things fi rst.
52. Code reading exercise Dependency graph The goal of this exercise is to get a feel for the structure of the code. (5 min) Independently - Examine structure Variables 1. Go through the code and underline all variables 2. Then draw a link between variables and their uses Function / method calls 3. Go through the code and circle all methods / function calls 4. Then draw a link between methods and their invocations Instantiation 5. Go through the code and draw a box around all instances of classes 6. Then draw a link between classes and their instances
53. Code reading exercise Most important lines The goal of this exercise is to start to think about which lines in the code de fi ne its essence, have the biggest impact or need to be paid close attention to. (5 mins) Independently - Identify most important lines Brie fl y discuss what it means to be important as a group (if you want to). Then, identify the 5 lines you consider most important.
54. Code reading exercise Concepts (5 min) Individually - Central thematic concepts Name the 5 most central concepts of the code. These could be names, themes, classes, or information found in comments.
55. Code reading exercise Summary The goal of this exercise is to think about the core purpose or function of this code. (5 mins) Independently - Summarize Try to write down the essence of the code in a few sentences.