What does this have to do with unit tests?
/!\ Unit tests != Quality
Absolutely nothing. And that’s my point.
What leads to quality is something much bigger—more than a collection of software engineering techniques or a collection of practices.
When I entered this community I was under the false impression that if you didn’t write software the way I did, you must be doing it wrong.
Instead I discovered a community that cared more about quality than I did, and that I still had a lot to learn about crafting a quality experience.
That’s what this whole things has taught me. It’s not about the practices. It’s about the spirit, intent, and in which they are applied. Used when applicable. Quickly abandoned when not.
Retour aux fondamentaux : la question n'est pas "comment gérer les tests unitaires ?" mais "comment gérer la qualité ?".
And they have snapped, accidentally, dozens of those carriers' lines, because even not-so-secret commercial lines sometimes don't show up on utility maps. Goguen, the utility manager, estimates that the rail project has already hit three dozen lines, sometimes doing no damage and other times grinding work to a halt or cutting power to retailers along Route 7. Even after extensively researching land records and maps and digging more than 600 test holes to determine utility locations, it's hard to avoid accidents on a project of such complexity and in such a busy place, he said.
Voilà ce qui se passe quand on fait de l'agile : ça sprinte, ça sprinte, et 3 ans après, il faut un démineur :-)