Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Frankly, the whole field of QA in programming was created only for fitting into the whole manufacturing process mindset.
Usually I like to build a beautiful piece of software, and think through the various ways it could be broken, or exploited. Having said that, on a manufacturing line, if you're looking to speed up processes, you cannot have the same machine building something AND making sure it came out just perfect.
So you break it into stages, which can run in parallel, and validation can feedback into the build.
That's all we've also been reduced to, a bunch of machines churning out code on one end, with a bunch of other machines with a knack for detecting changes in a repetitive process on the other end.
Don't fret though, unlike a machine, you can learn skills that can move you between these stages, depending on where your skill generates most value for the powers that be.
P.S. QA isn't sexy to programmers, the same way programming isn't sexy to management. :)
Stackoverflow.
For those of you who are having interviews ... remember this
I really miss having a team. Don't get me wrong, right now I do what I love and I got into a position where I can actually do Quality Assurance instead of just testing and I enjoy being able to actually change things instead of just repeating what problems there are and acting surprised when the same processes produce the same bugs over and over again but I really hope that we'll interview anything else than mouthbreathers soon.
I'm aware of the fact that QA isn't sexy and that few people who could become "Software ninja Rockstars" choose to go into it but can it be that hard to find at least two or three people who can write and read code at least on a junior level and understand how web protocols work? I get the feeling my entire branch is nothing but shit talkers clicking around blindly on pages.
I just want to exchange ideas again, come up with innovative tools, tweaking processes, learning from and teaching each other while we watch the entire operation get more and more efficient.
rant
team
incompetence
interview