A Staff Engineer's Guide to Inventing Work
- ID
- 30277
- Status
- summarized
- Published
- 28 Sep 2026, 10:46 PM
- Fetched
- 30 Sep 2026, 8:55 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://sujithjay.com/inventing-work
- Source URL
- https://hnrss.org/best
Summary
- Score
- 6.5
- Created
- 30 Sep 2026, 8:56 PM
- Tags
- Audience
- developerssaas_founders
What happened
Sujith Jay Nair's essay argues that platform teams are engineering-led, so 'work does not exist unless an engineer invents it' - the staff engineer's job is to read signals from four directions: the systems, the users, the organization, and the industry. In the systems section he covers crash-led discovery (postmortems as a maximally lagging indicator that biases teams toward the loudest, most recent failures), cost (cloud bill, business-unit P/L, vendor contracts, and treating buy-versus-build as a revisitable decision rather than a one-time one), and your own toil - with the caveat that your toil is not your users' toil. It drew 299 points and 58 comments on Hacker News.
Why it matters
If you run or sit on a platform/infra team with no PM and no revenue line, this gives you a concrete checklist instead of waiting for a roadmap: pull your business unit's P/L or cloud bill line-items, list vendor contracts and ask what pulling each function in-house (or farming it out) would cost, and mine postmortems for cross-incident patterns rather than reacting to the last outage. The actionable reframe is that buy-versus-build should be re-opened as team size, scope, and vendor pricing change - a decision most teams make once and never revisit. There is no Malaysia- or SEA-specific hook in this piece; treat it as general platform-team practice.
Discussion angle
Ask everyone to name one thing their team decided to buy or build more than a year ago and whether the original reasoning still holds - the essay's claim that buy-versus-build is not a one-time decision is the part most teams actually fail at.