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
- 2 courageous thinkers getting together is a beautiful thing 😀@CBrownRiver @flowchainsensei #rw14july https://t.co/IOB3EUTV8F 1 week ago
- @flowchainsensei Hey Bob, Can't make #RW14July :-( but @CBrownRiver is taking my place :-) say hello, we share a love for your writing 1 week ago
- RT @RiverAgency: Doing things the River way today! Having a lunchtime BBQ to say thanks & celebrate some recent team achievements #rewardan… 2 weeks ago
- @CBrownRiver Wow incredible 😀nicely done looking forward to hearing the stories 1 month ago
- RT @CBrownRiver: River are looking for passionate & experienced .NET developers to join one of our 6 development teams. Fancy a change? htt… 2 months ago