3 ms·
I think the problem is that code that passes manual QA testing is fine until it suddenly isn’t. That may be due to the complexity of the code base, the turn aro
by aardvark179 4y ago
I think the problem is that code that passes manual QA testing is fine until it suddenly isn’t. That may be due to the complexity of the code base, the turn around time on doing those tests, the accuracy of people following scripts, or just the number of tests and the size of the code base.
Similarly integration tests are fine until they suddenly aren’t, and you really need things like unit testing.
Unit testing also only works up to a point without tools to reason about the entire codebase and how it interfaces with others.
Organizations flourish or flounder based on recognizing when they are approaching those points and dealing with their underlying issues. Maybe AIs can write code that is good enough in a lot of cases, but unless people can understand that code and how to work with it and refactor it as things grow then they may not be a good idea.
- brundolf 4y agoAll of those things are true, and yet, that's how a lot of software is built in practice because it still ends up "close enough". The market has shown that this is acceptable in a whole lot of domains I'm not saying I like it, I'm saying it's the reality