OP, are you the author? If so there are a few typos I'd like to help you fix. Regarding the article, I'm a little bit shocked that unit testing is part of the

OP, are you the author? If so there are a few typos I'd like to help you fix. Regarding the article, I'm a little bit shocked that unit testing is part of the conversation at all. Firstly, I would consider unit testing to be an intrinsic part of software development, not a separate process with separate tooling that got tacked on as an additional task (like, for instance, needing to learn how to use Kubernetes). There's a lot to complain about in the industry regarding tooling complexity, but the author doesn't actually get into it at all. The only thing they seem to go into detail about is how unit testing makes writing code more difficult / slow, and a paragraph on React. And then there's this 'graph -- and while relatable, it has nothing to do with the general thesis: > A big gripe I have with how software developers are often expected to operate is that they are often told what the requirements for the software are by a BA or some other liaison between them and the business [...] Yes, this is an incredibly frustrating part of software development, but again, it doesn't have anything to do with tooling and all the software surrounding actually writing code, which is what the article seems to have been about originally.