3 ms·
> having to dig in and learn the fundamentals on a lot of things - which is unsustainable if you are touching 30-50 different technology stacks. IMO, this is t
by sgarland 3y ago
> having to dig in and learn the fundamentals on a lot of things - which is unsustainable if you are touching 30-50 different technology stacks.
IMO, this is the crux of the problem, and it’s caused by allowing dev teams to use whatever stack they want, without also requiring them to support it. More cynically, it will always be the case if teams are allowed to use whatever they want, regardless of “service ownership” – because when there’s a SEV-1 and the owning teams have no idea what’s wrong, the SREs are going to be told to fix it.
- meiraleal 3y ago> More cynically, it will always be the case if teams are allowed to use whatever they want Are you a manager? My cynical take is that this happens when managers choose tech as they know nothing and push for LinkedIn driven development
- sgarland 3y agoNope, SRE/DBRE. I’ve seen both absolute freedom and a centralized authority for choosing tech stacks. The latter was waaaaay more stable.