Grr. I’m sick and tired of rubbish specifications, poorly defined acceptance criteria, and the code that meets it. If you put shit in, you’re going to get shit

Grr. I’m sick and tired of rubbish specifications, poorly defined acceptance criteria, and the code that meets it. If you put shit in, you’re going to get shit out. Quality is what seperates the shit from the good. If no one on your team knows what quality looks like, or worse, they like the smell of shit, you’re getting shit, and everyone is going to pat themselves on the back like it’s a job well done. Quality isn’t conceptually hard. It’s the result of thoughtfulness, care, and dilligence. Three seemingly unwelcome qualities in a lot in software development settings. Any attempt to codify what quality is beyond that will dimish the significance of those pre-requisits and embolden those that don’t possess them. Quality is also the first thing you sacrifice when you offshore your development, and that’s something no ones wants to talk about. That’s not to say offshore teams are incapable of achieving quality. It’s to say that the rules of offshoring incentivise against quality and guarantee that your flawed specifications and requirements will be met with brutal efficiency and go unquestioned.