Dependencies in Software Development have been an issue since decades and lots of practices have been built to “manage” them, creating an environment that becomes more complicated with longer time-to-market times as dependencies grow (or the product/solution grows).
This is creating an illusion and no dependency management is alwys the only answer! Coordination to remove dependencies is usually a more sustainable outcome with less management.
I have attended several software craftsmanship and testing unconferences and similar events over the past years and all of them have left me wanting more. The openness, the sharing of knowledge and the freedom to fully decide on my own learning experience have been enough to inspire me to bring this wonderful concept to Belgium.
Last week, on 30 and 31 May, I attended the I T.A.K.E. unconference in Bucharest, Romania. I was asked to facilitate a workshop there and chose to combine two of my personal favorite coderetreat sessions into one even more challenging session: TDD as if the baby meant it. I will write about this session and some of the feedback I got on this soon, so keep an eye on this blog. During and after the conference I spent a lot of time talking to several people who are passionate about software craftsmanship like me. And these conversations triggered something in me again.
Recently I get a lot of questions related to Technical Debt and Legacy products which triggered me to write this article, explaining how I managed technical debt a while ago. I want to share this information to provide you extra options, I do not claim this system is the best out there, it is just one of many but definitely worth a try.