4 ms·
That only works for extremely simple projects with very small teams working on "hobby projects". For anything serious you need an independent and professional Q
by flohofwoe 6y ago
That only works for extremely simple projects with very small teams working on "hobby projects". For anything serious you need an independent and professional QA team which essentially does nothing else than trying to break the product all day in and out.
Programmers should be required to do enough local testing to not break the build of course, but the same person who wrote the code can't also thoroughly test it, because they'll inevitably only test the "happy path", even if they don't intend to.
- delfinom 6y agoThere comes a point though when theres too much QA that seriously hampers development and progress because they turn the smallest change into a year long shitfest of "hold on we are testing!". Microsoft for awhile got a bit heavy on QA, unforunately they also went full retard the other direction.
- Google234 6y agoI wonder how Google, MAFT, and Amazon do anything more than hobby projects!?