Discussion about this post

User's avatar
moonshadow's avatar

"It sure sounds like science is awesome and in this case straightforward, using it more would quickly let us figure out how to do it cheaply and at scale, and something about the way we ‘prove’ things is getting in the way. It’s a policy choice."

Compare: I've done some manual tests and it works on my machine. It sure sounds like my patch is awesome and in this case straightforward, and deploying it to production would quickly let everyone take advantage of the new feature. It's just something about the way our CI pipeline 'tests' things getting in the way. Formalised testing is a policy choice.

...If specific tests are flaky or superfluous, that's an argument about specific tests, not an argument for getting rid of quality assurance as a concept. I've been on call for unexpected prod failures caused by innocuous-seeming changes that worked just fine in local testing, and I don't wish the medical equivalent on anyone. With the greatest respect, please do not argue for doing to my healthcare system things no software engineer would want done to their QA / CI pipelines.

Jonathan Weil's avatar

>I would caution that it is very much not true that ‘the only parents who get schemed against by their kids are control freak parents.’ Most kids scheme against their parents to some extent, often quite a lot, even without provocation. It’s normal.

Yes, I fully endorse this, but would add that, as an anti-control freak parent, I find that the (near-constant) scheming is extremely low-effort when it comes to actually disguising it from me. Like, they will literally tell me that they are about to execute a “secret plan”…

28 more comments...

No posts

Ready for more?