proomt

Search

Search posts, papers, and topics

All posts

Hacker News front page5 min readintermediate

Doing Everyone Else's Job

Summary

The author argues that taking on tasks outside your formal role gives insight and can accelerate delivery, but warns that such “charity” can hide deeper organizational problems like misaligned incentives around buy‑vs‑build and centralization.

  • Doing work outside your role reveals hidden dependencies and can unblock projects.
  • Integrating a feature directly into another team's system can sidestep slow planning cycles.
  • Buy‑vs‑build and centralize‑vs‑roll‑your‑own decisions often reflect headcount incentives more than technical merit.
  • Relying on a tiny minority to do others' jobs masks systemic issues and risks burnout.

Senior engineers and engineering managers should read it to understand the trade‑offs of cross‑functional work and avoid hidden inefficiencies.

4/10

Related reading

  1. How Orange uses agents to make FinOps everyone's responsibility

    Orange created a FinOps Community of Practice and runs ‘Clean Days’—protected, gamified sessions that get engineers actively optimizing cloud spend. They then scale this culture with AI agents that surface cost data, suggest quick‑win fixes, and automate reporting, extending responsibility across thousands of engineers.

    Google Cloud Bloggoogle.com4 min
  2. The pursuit of excellence does not need justification

    Opinion piece arguing that engineers should pursue excellence without needing to justify it, using anecdotes about a fast terminal emulator and a WordPress menu cache to illustrate how over‑engineering can yield unexpected downstream benefits, while also acknowledging the practical need for “good enough” decisions.

    Bjørn Johansenbjornjohansen.com2 min
  3. Article: Beyond Relevance: A Governance-First Architecture for Enterprise Personalization

    The article proposes a governance‑first architecture for enterprise personalization, where policy‑driven steps (memory, journey graph, AI routing, scoring, trust checks, outcome simulation) shape the recommendation before it is returned. A reference FastAPI implementation demonstrates the pattern with external YAML policies and optional LLM assistance.

    InfoQinfoq.com19 min
  4. Podcast: Signals and Levers: Building Thriving Engineering Organizations

    The podcast explains how systems thinking helps leaders grasp the complex, adaptive nature of software delivery, especially as AI rollouts amplify bottlenecks. It also outlines cultural "levers"—choices that shape unwritten rules—to build sustainable, fun engineering teams.

    InfoQinfoq.com31 mintalk