> a successful compile means no bugs Isn't that a strawman? Shouldn't we verify to what extent this mentality actually develops (I doubt it) rather than rebuil

> a successful compile means no bugs Isn't that a strawman? Shouldn't we verify to what extent this mentality actually develops (I doubt it) rather than rebuild our methodologies around it - or at least begin by simply educating developers directly about the pitfalls of this assumption. Sometimes it feels like treating developer flaws as unfixable constants that can only be handled by process change, as opposed to developer improvement. Perhaps a symptom of hiring the cheapest devs en-masse?..