Spent the day tackling complexity and wondering how it all got there. We’ve gotta keep refactoring if we are going to get a grip on the product. My first solution to a nasty bug failed the code review. Talking it over the penny dropped and the bug was fixed with a change to a single method. It turned out to be a case of mistaken responsibility and a change of object was all that was needed. Why does talking about a problem, or for that matter writing about it, make it clearer? In this case my victim wasn’t technical and I think that helps, you need to take another step back and make things completely clear if they’re going to understand and that seems to inspire new solutions.
Come say hello at...
No upcoming events
- RT @cheltenhamgeeks: We’re back on thanks to some help from @CBrownRiver and @rippo: Headless UI testing with Chrome and Puppeteer https://… 6 days ago
- New Blog Post: “How Agile thinking can liberate the workplace” email@example.com/h… 1 week ago
- RT @RiverAgency: Wow, what a year! Today's our last day in the office before a well deserved rest with friends & family. Happy Christmas to… 3 weeks ago
- @CBrownRiver Yikes. Watched @WeAreTheCircle last night and kept wondering if it was an insite into the future of @RiverAgency ;-) 1 month ago
- RT @adampknight: Posted yesterday on using the 'Myths of Creativity' to establish a principled approach to Innovation in my organisation ht… 2 months ago