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
- @MrABriggs @cheltenhamgeeks Hi, it’s dormant atm I’m afraid. Not really sure when I’ll be able to resurrect, curren… twitter.com/i/web/status/1… 6 months ago
- Today’s bread came out with teeth! https://t.co/6MNnPfFJB9 7 months ago
- RT @teamrivertweets: Is sharing meaningful data the key to unlocking productivity in your business? Download our new report to find out >>… 9 months ago
- RT @teamrivertweets: This isn't just a continuous improvement tool. This is the only product that combines your business data with social c… 11 months ago
- RT @teamrivertweets: White Paper | Get our free white paper to learn how to unlock a culture of 'Innovation Everywhere'. @diaryofscrum expl… 11 months ago