There’s really only one key practice for quality: continuous improvement, and its dual, continuous learning. For continuous learning, many practices that help; one of my personal favorites is ‘Lunch and Learn.’ It’s easy to get started, allows the team to ‘opt in’ to shared practices, and is an amazing opportunity for growth.
One example that quickly springs to mind is “Clean Code: A Handbook of Agile Software Craftsmanship” by Robert Martin. This was one of the featured books in our lunch and learns at EVault. We’ve also done this at Pharmatrust, and I think we’re about at critical mass to do this at MedAvail.
On a side note: I consider myself fortunate to have had the opportunity to learn from the teams I have worked with over the years; it’s one of the greatest pleasures of my professional life.
After yesterday’s (somewhat lame) post on Beautiful Code, I realized that there have been a number of books I’ve read, source code I’ve read, and projects I’ve participated on that have influenced my sense of software style and craft.
While most lists like this emphasize the computation books, I’ve noticed that there’s an implicit book missing from most of these lists, namely “The Elements of Style.”
Here’s my top set of core books on coding style that I really thing matter:
- The Unix Programming Environment, by Kernighan and Pike,
- The C Programming Language, by Kernighan and Ritchie,
- the various ‘Lambda papers’ Guy Steele (Lambda, the ultimate imperative, etc.)
- the Anatomy of Lisp by John Allen,
- On Writing Well, by Zin
- The Elements of Style by Strunk and White,
and, influenced by Strunk and White:
- The Elements of Programming Style, by Kernighan and Plauger
- The Elements of Java Style, by Vermeulen, Ambler, Bumgardner, Metz, Misfeldt, Shur, & Thompson
Interesting overlap with the list over at the Association for Computing Machinery (Classics).
What influenced you?