Qkrzo04vt5ypkgpj3occ
SkillsCast

BDD Alchemy: Change your Heavy Lead (Pb) Code into Pure Gold (Au)

8th November 2018 in London at CodeNode

There are 33 other SkillsCasts available from P3X - People, Product & Process eXchange 2018

Please log in to watch this conference skillscast.

Https s3.amazonaws.com prod.tracker2 resource 41088130 skillsmatter conference skillscast o9nohu

How to continuously deliver more and more value? You’ve read Clean Code, you are writing SOLID code, you are a true craftsman. You are proud of not letting any technical debt behind you. You are applying DDD and BDD, and discussing with your users to clarify what needs to be built.

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:

Thanks to our sponsors

BDD Alchemy: Change your Heavy Lead (Pb) Code into Pure Gold (Au)

Philippe Bourgau

Philippe Bourgau, Continuous Refactoring Coach,

SkillsCast

Please log in to watch this conference skillscast.

Https s3.amazonaws.com prod.tracker2 resource 41088130 skillsmatter conference skillscast o9nohu

How to continuously deliver more and more value? You’ve read Clean Code, you are writing SOLID code, you are a true craftsman. You are proud of not letting any technical debt behind you. You are applying DDD and BDD, and discussing with your users to clarify what needs to be built.

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:

Thanks to our sponsors

About the Speaker

BDD Alchemy: Change your Heavy Lead (Pb) Code into Pure Gold (Au)

Philippe Bourgau

Philippe Bourgau, Continuous Refactoring Coach,

Photos