Please log in to watch this conference skillscast.
Everything is going fine until the day when, during an informal conversation, you understand something deeper about your domain … This is called a ‘refactoring breakthrough’. Suddenly, everything changes, you start dreaming up a new design that would both simplify your life and make you more effective.
Something else has changed: your technical debt. It just doubled overnight! Whereas yesterday you felt productive, today, you feel slow in the light of what this new design would enable. Interestingly, it’s BDD and the discussions with users that put you in this situation. That’s strange, isn’t it?
That a best practice would create technical debt looks like a nonsense! Should we rethink the whole notion of ‘technical debt’? How does BDD unlock these ‘refactoring breakthrough’? How can we benefit from this opportunity? What’s at stake here?
YOU MAY ALSO LIKE:
- Flexible Architectures: Microservices, Self-contained Systems and Continuous Delivery with Eberhard Wolff & Niko Will (Online Workshop on 22nd - 24th February 2022)
- Evolution and Improvement of Software Architectures with Markus Harrer (Online Workshop on 21st - 23rd March 2022)
- Understanding Microservices: A Guide for the Monolithic Developer (SkillsCast recorded in October 2021)
- F# Gives You Superpowers (SkillsCast recorded in October 2021)