3 ms·
> doing Quality Assurance work So I am guessing if he was actually a developer to begin with his job would have been a bit harder to automate.
by smegel 10y ago
> doing Quality Assurance work
So I am guessing if he was actually a developer to begin with his job would have been a bit harder to automate.
- minimaxir 10y agoSpeaking as a QA Engineer myself, QA is as rigorous and important to the software lifecycle as development. The continual disrespect for QA engineers is somewhat frustrating.
- smegel 10y agoThe point I was making is you don't become a tennis player by kicking a football.
- geofft 10y agoFrom the Reddit post: > I got a job as a software developer working mostly on testing software, so mostly QA work. However I actually had to write some code as well. After around 8 months I had basically automated my own job by writing some programs to do it all for me. It certainly doesn't look like a manual QA job. The part that surprises me is that the tests didn't change for six years. Surely after 6 years something about a codebase changes (the build infrastructure changes, a new platform shows up, the API changes, etc.) that even black-box testing would have to adapt. Did the company not care that much about the accuracy of the tests?
- MBCook 10y agoThis sounds like a management issue more than anything else. The guy screwed up, but how did no one catch on for 6 years? How did he not have someone managing him making sure he had enough work? Seems like he 'fell through the cracks' of startup culture. The company grew so fast that he was just there and no one questioned it after a while and no one was in charge of him. Or someone was and they need retraining/firing.