I used to think that writing tests was a fancy option that web frameworks allowed you to do when there was nothing else on the agenda 😄. Honestly, it wasn’t my fault! To me, it seemed impossible that such a fundamental practice was never emphasized (let alone taught) in all those university courses and online tutorials. However, reality hit hard. At a particularly complex job, we produced bugs faster than features, and it dawned on me that there had to be a more effective way of working. In a nutshell, after thorough investigation, research, and a healthy dose of Dave Farley’s videos, I made a conscious shift. I dedicated more time to refactoring and allocated a portion to writing tests (though not quite full-blown TDD). The results became evident within weeks for me and within months for others. So, based on my experience, if you genuinely care about improvement, you’ll discover the path to doing better-and others will follow suit when they witness the impact. 🚀
That's a really encouraging story! Thanks for sharing your experiences. I think you're right - once people have realized the impact of practices like refactoring and writing good tests they will want to work this way too.
I'm a technical coach at work: I've embedded myself in a team and used pair programming on tasks to support the team in practising TDD, or through code katas in 1:1 coaching sessions.
I used to think that writing tests was a fancy option that web frameworks allowed you to do when there was nothing else on the agenda 😄. Honestly, it wasn’t my fault! To me, it seemed impossible that such a fundamental practice was never emphasized (let alone taught) in all those university courses and online tutorials. However, reality hit hard. At a particularly complex job, we produced bugs faster than features, and it dawned on me that there had to be a more effective way of working.
In a nutshell, after thorough investigation, research, and a healthy dose of Dave Farley’s videos, I made a conscious shift. I dedicated more time to refactoring and allocated a portion to writing tests (though not quite full-blown TDD). The results became evident within weeks for me and within months for others. So, based on my experience, if you genuinely care about improvement, you’ll discover the path to doing better-and others will follow suit when they witness the impact. 🚀
That's a really encouraging story! Thanks for sharing your experiences. I think you're right - once people have realized the impact of practices like refactoring and writing good tests they will want to work this way too.
I'm a technical coach at work: I've embedded myself in a team and used pair programming on tasks to support the team in practising TDD, or through code katas in 1:1 coaching sessions.
I'm happy to hear that you're a technical person with coaching skills. I wish you and your team every success practising TDD!
@@EmilyBache-tech-coach all credit to you and the channel for keeping me inspired.