TL;DR: Reading Code Is Harder Than Writing It
It’s funny that computer languages are the only languages where one learns to write before learning to read. It’s actually not uncommon for people to never really learn to read code. This seems a little unbalanced given that we actually read code much more frequently than we write it.
Even those who promote software as a craft sometimes fall into the trap of often talking about writing clean code that people can read, yet not placing much emphasis on the skill of reading the code.
The ability to read code must also be a skill, and as such it must be something that can be learnt and practiced. In this presentation, we’re going to look at:
- The different reasons we might have to read code, and how that should impact our reading
- The problems we face when reading code (even our own!)
- Tips to bear in mind when we're reading code
- Tools we can use to help our understanding
- How and where to practice these skills
At the end of the talk we will at least have considered whether we need to level up our “Reading Code” skill.
What will the audience learn from this talk?
The audience will learn the value of concentrating on the skills of reading the code, without in isolation to any code-writing. The audience will pick up some tricks on how to improve their ability to read code.
Does it feature code examples and/or live coding?
Yes, both code examples and live coding.
Prerequisite attendee experience level: