News for hackers. Stuff that matters.
Re:The Google incentive mismatch: Problems with promotion-or... by Manuel_D on Wednesday May 04, 2022 @01:48PM (#31263626)
At some companies, this is broadly what "SRE" vs "SWE" is meant to capture. But the issue is that roles aren't very fluid, plenty of times SWE ends up transitioning to a role more resembling an SRE after building a system and reorienting towards maintaining it.
Re:The Google incentive mismatch: Problems with promotion-or... by joshuamorton on Wednesday May 04, 2022 @02:48PM (#31264344)
God I hope not, SRE isn't a maintenance engineering role!

Improving the reliability of a system (SRE's ultimate responsibility) is deeply technically challenging work of its own, and one can encounter deeply challenging problems.

Re:The Google incentive mismatch: Problems with promotion-or... by Karrot_Kream on Wednesday May 04, 2022 @03:16PM (#31264648)
The problem is that people think "maintenance" is a bad word. A company like Google is seeing growth from external customers, churn from their internal systems as internal best practices change, and changing threat landscapes on the internet.

"Maintenance" often is actual hard feature work. But when your org or company has a culture of thinking of maintenance as some low-level job, you get a culture like Google's.

Re:The Google incentive mismatch: Problems with promotion-or... by joshuamorton on Wednesday May 04, 2022 @03:51PM (#31264965)
I don't disagree. I don't think maintenance is a bad word. But I do think that there is a point beyond which "maintenance" cannot grow. If you're maintaining a system there is a breadth of experience you cannot get. Being a senior engineer at Google is not easy. But my point is that sre is still fully capable of supporting L7 and L8 ic swes, while "maintenance" isn't.