I did a presentation called “communication in code”, about the importance of writing communicative code which is easy to read, understand and therefore to maintain.
Writing clear and expressive is more important than writing working code, as if you communicate well than others can take your work and build on it. If not, it simply has to be thrown out when it stops being directly useful.
- Clean Code - Uncle Bob / Lesson 1
- What is self-documenting code and can it replace well documented code?
- Small Functions considered Harmful
- Wikipedia: Self-documenting code
There’s also a video of my presentation (available to Canonical employees only).