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 @teamrivertweets: Bring data together in a collaborative space with River to unite teams and revolutionise the way your business works.… 8 minutes ago
- RT @teamrivertweets: #Inspiration | How agile thinking can liberate the workplace. Is an #agile mindset useful for any organisation regardl… 6 days ago
- Here’s a blog post I’ve been working on for our new product website teamriver.com What do you think? twitter.com/teamrivertweet… 1 week ago
- RT @RiverAgency: Why do some people take charge of #happiness and others don’t? Listen to our CEO, Phil and COO, Tom on the @Happy_Melly po… 2 months ago
- Podcast: @phildunk and I chat about Liberating People at Work with @Happy_Melly happymelly.com/liberating-peo… 2 months ago