4 ms·
This is a great article from Jess - as all her writing is. The only rejoinder I will make here is that in my experience doing enterprise dev, the software is b
by listless 5y ago
This is a great article from Jess - as all her writing is.
The only rejoinder I will make here is that in my experience doing enterprise dev, the software is bad because there is little or no QA.
I only worked in one enterprise where the dev director hired a single QA engineer. This lady checked all of my code from end to end every time I thought it was ready to ship. It took me 3 months to do something I thought I could do in one because this lady caught EVERYTHING. I hated her for it. She made me fix every single bump, every pixel. Everything. And when we shipped it, it was the best software I have ever written and one of the best pieces still running.
- elboru 5y agoI love writing automated tests, but having someone else test your own code is just different, I as the owner of the code will usually have a “positive” attitude to my own code, this in my opinion limits my imagination towards all the things that can go wrong (TDD sometimes helps me but it has its limits). On the other hand, a QA tester has a “negative” attitude, he or she knows that there are bugs in the code and his/her work is to find them.
- listless 5y agoYeah - you can’t beat an indifferent 3rd party. They’ll find all the stuff that you either code around or innately know not to do.