undefined | Better HN

0 pointszsoltkacsandi2y ago0 comments

My experience is (as a former dev, current ops) that the problem isn’t that dev and ops people aren’t speaking the same language, nor the tooling or processes.

The problem comes from the management/business side. They hire devs and tell them that ship features as fast as you can. Also they hire ops guys and tell them that I want this whole thing super reliable, we can’t afford a minute downtime.

In my opinion this is why DevOps is mostly pointless. We are trying to fix with tooling, processes, new tech, and fancy roles the fact that business people don’t want to make compromises or choose between the pace of delivery and reliability.

0 comments

hinkley2y ago

That’s definitely part of the dynamic. My biggest regret with automated testing is that software used to be a triumvirate of Quality, Dev, and Management, and when dev was fucking around they had two teams hitting them, and when Management was out of control, they had everyone mad at them. Get rid of QA and it’s Us vs Them and that worked briefly at the dawn of Agile but they got wise.

OP’s should replace QA at that table to rebalance the equation. But again, and as you illustrated, we have an adversarial relationship that takes a lot of across the aisle work to introduce sanity.

convolvatron2y ago

I agree. but having a QA group was hardly a magic bullet. most of the really talented contributors eschewed QA - even if they enjoyed it - because it meant being identified as a QA person for the rest of their career.

even if you could staff a competent group, they are often left with nothing to do while the devs 'work their magic'. and suddenly its 3 months past the original 'functionally complete' deadline, and QA is given 1 week to do what they .. oh, maybe 3 days really, to do what they need to do.

when it works its irreplaceable. when it doesn't its just a lot of noise and spend and flailing.

cmrdporcupine2y ago

The most productive QA/dev team experience I had back in the day was in a shop that was playing with eXtreme Programming and we did little 2-3 person strike mission per-issue groups with 2 to 3 devs and 1 QA person. Work on strictly defined small feature and continuously QA through the process, and then iteration end the QA person worked more intensely. The point being that the QA staff was treated like another development engineer even if they weren't writing code, so no "toss this over the fence to QA" and "oh god this is horrible, the devs are shit" mentality. Outcome of the feature was not just completed code, but (hopefully) test plans and sign-off from QA.

The QA people hated it though.

hinkley2y ago

I would definitely say that some of the finest and worst people I’ve worked with were in QA. Mercifully usually not at the same job. It can be a great place to push ideals, or to hide from them.

I know why it’s gone, I’m just not happy about it.

j / k navigate · click thread line to collapse

0 pointszsoltkacsandi2y ago0 comments

My experience is (as a former dev, current ops) that the problem isn’t that dev and ops people aren’t speaking the same language, nor the tooling or processes.

0 comments

hinkley2y ago

OP’s should replace QA at that table to rebalance the equation. But again, and as you illustrated, we have an adversarial relationship that takes a lot of across the aisle work to introduce sanity.

convolvatron2y ago

when it works its irreplaceable. when it doesn't its just a lot of noise and spend and flailing.

cmrdporcupine2y ago

The QA people hated it though.

hinkley2y ago

I would definitely say that some of the finest and worst people I’ve worked with were in QA. Mercifully usually not at the same job. It can be a great place to push ideals, or to hide from them.

I know why it’s gone, I’m just not happy about it.

j / k navigate · click thread line to collapse