3 ms·

I think the analogy with QA deserves some credit here. "Testing" as a part of software process has not gone away, but the people who solely did QA are now gone

I think the analogy with QA deserves some credit here. "Testing" as a part of software process has not gone away, but the people who solely did QA are now gone - either evolved into doing both dev and qa; or moved to companies where the older processes still exist. Testing was more closer to writing-code - so that got absorbed into the dev side faster. Disappearing QA was a you-blink-and-you-miss revolution. DevOps is a little farther. Several developers are not able to wrap their heads around the deployment systems, the implications of hardware and network etc. But they will. Eventually. Because they are smart people. I think the message of the article is that people who solely have DevOps expertise, should look to evolve to developing code as well. That way we have smaller, well-knit teams with each member having an additional speciality other than writing code.

HashHishBang 11y ago
My current job seems to disagree with you and their point about QA. As far as I've been able to see, the market explicitly for QA Automation is actually growing. The idea of >Developers are responsible for full test automation and making sure their code works. Is laughable outside of [insert new sexy startup here], if only due to the difference in mindset. Granted I'm totally biased as a QA Automation, but the analogy actually removed quite a bit of credence that this article might otherwise have held with me.
- pilom 11y ago
  Idk, QA Automation is growing but that has rapidly replaced TONS of "follow the procedure by hand" type QA specialists. People who knew how to write procedures well and document executing them well are disappearing in droves to 1-2 people who write QA Automation scripts in Selenium or something.
  - HashHishBang 11y ago
    Yeah I can definitely see that side of things. The manual aspect of QA is definitely reducing, though I would hesitate to call it entirely dead. I love the fact that I've got experienced manuals who are able to craft well written procedures that I can automate. There are more and more opportunities for QA Automation with the ability to write those procedures, which I suspect are the ones replacing the manual QA specialists you reference.

HashHishBang 11y ago

My current job seems to disagree with you and their point about QA. As far as I've been able to see, the market explicitly for QA Automation is actually growing. The idea of >Developers are responsible for full test automation and making sure their code works. Is laughable outside of [insert new sexy startup here], if only due to the difference in mindset. Granted I'm totally biased as a QA Automation, but the analogy actually removed quite a bit of credence that this article might otherwise have held with me.

pilom 11y ago
Idk, QA Automation is growing but that has rapidly replaced TONS of "follow the procedure by hand" type QA specialists. People who knew how to write procedures well and document executing them well are disappearing in droves to 1-2 people who write QA Automation scripts in Selenium or something.
- HashHishBang 11y ago
  Yeah I can definitely see that side of things. The manual aspect of QA is definitely reducing, though I would hesitate to call it entirely dead. I love the fact that I've got experienced manuals who are able to craft well written procedures that I can automate. There are more and more opportunities for QA Automation with the ability to write those procedures, which I suspect are the ones replacing the manual QA specialists you reference.