How to mentor 

​Once you start getting experience, you’ll find other developers asking for your help. I started tutoring at university so that I could help, and reflect and improve my own knowledge.  Mentoring isn’t about answers. It’s about learning how to find the answer. The most interesting problems we deal with are the ones that no-one knows … More How to mentor 

Wings of desire – future-proofing software architecture

(Note: this was originally posted on a since-archived company blog, so apologies for those who’ve read it before) Architects are never quite sure how their buildings and common spaces are going to be used once real people move in. Just as software developers are never quite sure how their software is going to be used. … More Wings of desire – future-proofing software architecture

Why you, yes you, should present at conferences 

The best ways to learn are active, whether it’s Deliberate Practice, a proof of concept demo, or teaching someone else, anything is better than passively reading or watching a presentation. And presenting at a conference forces you to distill your learning into the pure essentials, to decide what’s important, where the roadblocks are, and tell … More Why you, yes you, should present at conferences 

Killing legacy code

Michael C. Feathers defines legacy code as code without tests. I find it’s also likely, as a consequence, to be heavily coupled, with deep tendrils interconnecting multiple components. Indeed, many of the patterns in his Working Effectively With Legacy Code are about how to sever those tendrils safely in order to test the components individually. … More Killing legacy code