In this episode of Hot Tech(e), Philippe Van Eerdenbrugghe and I talk about failure.
Mostly about how we keep saying that we should fail early, and then somehow manage to do the opposite.
We talk about bugs, TDD, experiments that become permanent by accident, product ideas that are not quite dead enough to remove, and code that was “good enough for now” until “now” became eighteen months.
We also talk about the emotional side of failure. Because a failing test does not feel like shame. But a failing feature? A failing design? A failing product bet? That is harder.
It was a really nice conversation about failing sooner, learning faster, and maybe not making engineers silently pay for every bad decision forever.
Philippe on LinkedIn:
https://www.linkedin.com/in/philippevaneerdenbrugghe
Nodalview:
https://www.linkedin.com/company/nodalview/
Provide SRL:
If you are looking for guidance, Philippe is a great coach for software engineers, tech leads, and CTOs.
