Best of Company Culture — March 2026

  1. 1
    Article
    Avatar of techworld-with-milanTech World With Milan·8w

    You're Not Paid to Write Code

    Engineers who deliver the most value aren't the fastest coders — they're the ones who think first, ask questions, and sometimes conclude that no code is needed at all. Code is a liability, not an asset: every line must be maintained, understood, and eventually changed. Jumping straight to implementation often means solving the wrong problem, as illustrated by a checkout performance example where the real issue was form complexity, not query speed. Organizational incentives (promotions tied to features shipped, not problems avoided) push teams toward code-first behavior. AI amplifies this: a 2025 METR study found developers were actually 19% slower with AI tools despite expecting to be faster, and GitClear data showed 4x more copied code. The solution is a 'thinking-first' approach — writing a short paragraph defining the real problem, who it affects, and how success is measured before touching the editor. Amazon's 'Working Backwards' process is cited as a model. The engineer's real job in 2026 is problem framing, architectural judgment, deciding what not to build, and validating AI-generated output — not raw code output.

  2. 2
    Article
    Avatar of hnHacker News·7w

    Is anybody else bored of talking about AI?

    A developer reflects on AI fatigue — the sense that online tech spaces like Hacker News have become saturated with near-identical posts about AI workflows and tooling, crowding out discussion of actual products and problems being solved. The author argues that management's obsession with AI metrics (like tokens per developer) mirrors the old 'lines of code' fallacy, and calls for a return to focusing on the value being created rather than the tools used to create it.

  3. 3
    Article
    Avatar of staysaasyStay SaaSy·9w

    Avoiding a Culture of Emergencies

    Well-managed teams experience far fewer emergencies than poorly managed ones. Four key practices separate good managers from bad: staying deeply informed about what their teams actually do, maintaining strong conviction about what work truly matters so they can push back on unnecessary requests, building a mental model of the team and business to anticipate future needs, and genuinely caring about team well-being. Emergencies are often a choice — the result of managers prioritizing short-term convenience over their team's long-term productivity. Reducing emergencies leads to happier teams, better retention, and the focused environment that great work requires.

  4. 4
    Article
    Avatar of terriblesoftwareTerrible Software·10w

    Nobody Gets Promoted for Simplicity

    Engineering teams systematically reward over-engineering while penalizing simplicity, creating perverse incentives from interviews to promotions. Engineers who build elaborate systems get compelling narratives for promotion packets, while those who ship clean, minimal solutions have nothing impressive to show. The post argues that unearned complexity is the real problem, not complexity itself, and offers concrete advice: engineers should document the decisions they didn't make and frame their judgment explicitly, while engineering leaders should change the questions asked in design reviews and promotion discussions to make simplicity the default rather than something that needs defending.

  5. 5
    Article
    Avatar of seangoedeckesean goedecke·6w

    Engineers do get promoted for writing simple code

    The popular belief that writing overcomplicated code leads to job security or promotion is largely a myth. Engineers who write simple, clean code tend to ship faster, accumulate more successful projects, and build reputations as reliable deliverers — all of which managers notice and reward. Non-technical managers may initially be impressed by visible complexity, but over time they track results, not perceived difficulty. Deliberately overcomplicating work backfires through slower delivery, more bugs, and complaints from teammates who inherit the mess. The real career advice: it's fine to frame your work as slightly complex, but actually doing unnecessary complexity is counterproductive.

See all Company Culture archives