3 ms·
Finance is my domain ... worked/working for large established companies ... no containers or k8s. Yes, there's some presence for R&D or maybe external web or e
by scrubs 3y ago
Finance is my domain ... worked/working for large established companies ... no containers or k8s. Yes, there's some presence for R&D or maybe external web or external search but absolutely nothing in front, middle, back office or connections to brokers, exchanges ie. where it's serious.
Now having written that the CD part does come with eye rolling ... i think of last emplyor which seemed to go out of is way to make prod changes small as possible, unorchestrated, paternalistic. Dev installs looked rather different than beta or prod so there was no incentive to improve. And that was fine with management.
Ultimately I think management didn't trust devs. So rather than process improvement it was better to go slow, beurceatric, make devs get approvals as implicit disincentive to change. In their mind devs were qino (quality in name only). Tls and middle managers did QA by approving or rejecting tickets.
Usually good companies think quality is everybody's problem and empower + train accordingly. And nobody serious about quality thinks QAing tickets is quality. No, it spends resources only. That's the only thing 100.0% of all people can agree on when it comes to inspecting quality into CD.
I'm fine with prod approvals but not for blow-by-blow changes
My current employer has far far stringent rollout requirements so elastic scaling et al isn't in scope. It's very planned, determative.
- 2rsf 3y ago> I'm fine with prod approvals but not for blow-by-blow changes I'm at banking and we use containers heavily, they are not just for scaling but also for ease of deployment. We still need approvals for changes in production, but the main reason for being strict with them is legal and less beurceatric. What did you mean by blow-by-blow?