Why Your Codebase Fights Change (And How to Fix It)
If you’ve worked with software for any length of time, you’ve seen it: a codebase that starts as a lean, focused system can morph into a costly, resistant beast without careful stewardship. I recently led a workshop on this topic, and it sharpened my perspective on what drives long-term success in development. What’s difficult isn’t implementing algorithms or optimizing data structures. It’s about ensuring that ongoing changes remain affordable, low-risk, and efficient. For those steering teams through the pressures of tight deadlines, growing systems, and collaborative demands, managing complexity is what keeps projects on track, budgets in check, and teams productive.
Read more…'Winter hats go with winter coats', and 'supporters instead of jailers'.
In my journey through various workplaces, I’ve noticed recurring problems that seem to plague most companies. Two issues stand out prominently: the pervasive presence of office politics and the diminishing capability of companies over time.
Read more…A vision for Web 5
Hype cycles in tech rarely translate to significant changes in our lifestyle. Technology is a wide topic, but let’s focus on information systems today, and leave energy, food, water, health, and other important topics for another time.
Read more…Interdependencies in your system of work, and how not to evaluate software practices
I hear of people saying their team tried Trunk-Based Development, and decided they didn’t find it beneficial after a couple of months. I’m not going to war about the benefits of Trunk-Based Development today, even if I do love this practice.
Read more…So you think you work in a team
I had a discussion on Twitter yesterday about whether a software development team should restrict the freedom of its members, and enforce shared approaches and ways of working. I and others were adamant that yes, this should absolutely be the case. Others were horrified, saying this is everything that’s wrong with our industry.
Read more…