5 ms·
Why is a developer deploying to production in the first place? To minimize the work for everyone the code should have gone through QA before it was passed to op
by runarberg 6y ago
Why is a developer deploying to production in the first place? To minimize the work for everyone the code should have gone through QA before it was passed to ops. Ops should be confident that QA did their job sufficiently (“A lazy programmer knows how to delegate”) and shouldn’t be afraid to start the deploy job whenever.
- mxz3000 6y agoNot all companies/teams have dedicated QA and Ops teams. In the (very large) company I work at, the engineers are responsible for writing the code, testing it, and supporting it once it's live. That includes being Oncall and being paged if something goes wrong.
- runarberg 6y agoFor a small company with a fairly stable feature release schedule, that is fine. But in a large setting where expectations for new features is high, that seems like a scam. That is it looks like they are trying to get the developer to work double (or triple) shifts but only pay for one.
- temporama1 6y agoDude, I'm so jealous that you haven't even heard of DevOps. I don't know where you must work but please give me a job.
- Silhouette 6y agoThe trouble seems to be that "DevOps" is the new "Agile". How often is it just an excuse to dump non-development responsibilities on the dev team, and to ignore boring but time-proven processes and tools that specialists might have preferred if you'd hired them for those responsibilities instead?
- jghn 6y agoWhy are there separate QA and Ops teams?
- tompazourek 6y agoOps usually understand infrastructure, and QA usually not so much. The overall mindset is a little bit different, i.e. QA tries hard to break it, and Ops tries hard to keep it running. And the required skills might also be different (distinct sets of tools, techniques, certifications, etc.) But I can see that it might be useful to have it all together... (DevOps, QAOps)