Hacker News Reader

I mean it sounds clever, but how do you have engineers with no expertise in a system handling calls for it? I've been at places that follow the sun, and you frequently have no idea what to do during an incident, because the person who owns the system is offline. But at least you can sit one a useless incident call during work hours instead of completing your own tickets I suppose.

View on HN

The point is that the "ownership" used to rhetorically justify the labor of such engineers is not "ownership" at all: it's missing the literal most important aspect, that is the ability to profit proportionally as a project brings in revenue. Literally everything else is included -- the intensity of work, the singular focus, the care and devotion, the expected level of initiative -- but not the part that would most benefit the engineer.

It's just rhetorical trickery.

There should be SOPs in place for each "expected" issue so people know what to do. Its not like you (should) start debugging and deploying stuff in the middle of your on-call shift anyway. Its not 100% for sure but in the normal case this should be fine.

Reply on news.ycombinator.com