Best of Company CultureApril 2026

  1. 1
    Article
    Avatar of swizecswizec.com·4w

    Frustration Driven Development

    Frustration is a powerful engineering signal. Instead of repeatedly doing the same manual task, great engineers use that annoyance as motivation to eliminate the problem permanently. Three concrete examples illustrate this: upgrading CI/CD runners to cut build times from 10 to 2 minutes instead of endless Slack debates; building a self-serve permissions UI so managers can grant roles without engineering involvement; and writing AI-assisted tests to cover complex invoicing edge cases that were impossible to reproduce manually. The core philosophy is that your job is to remove work, not just do it — build tools, scripts, dashboards, and automation that create durable value and eliminate recurring friction.

  2. 2
    Article
    Avatar of hnHacker News·2w

    Drunk Post: Things I’ve Learned as a Senior Engineer

    A preserved Reddit post from a data engineer with 10+ years of experience, written candidly after a few drinks. Covers career advice (change companies to advance, be honest with managers), technical opinions (SQL is king, best code is no code, TDD is a cult), data engineering specifics (Airflow, streaming, ML project failure rates), and life reflections. Touches on work-life balance, remote work tradeoffs, tech stack philosophy, documentation as an underrated skill, and the importance of kindness. Raw, unfiltered, and widely relatable.

  3. 3
    Article
    Avatar of staysaasyStay SaaSy·3w

    High Amplitude Disagreeableness

    Startup people share a distinctive trait called 'high amplitude disagreeableness' — they may not argue constantly, but when they do, they go all-in, publicly and persistently. This stems from a creator mindset rather than an extractor mindset. Managers who want to attract and retain entrepreneurial talent need to match that intensity themselves, build cultures that tolerate strong disagreement without punishment, and avoid being confidently wrong — because startup people will remember and hold it against you.

  4. 4
    Article
    Avatar of harasim-devHarasim.dev·5w

    Glue Work: The Invisible Effort That Actually Ships Products ‣ harasim.dev

    Glue work — the invisible labor of mentoring, refactoring, documentation, and team alignment — is what actually keeps software projects running, yet it rarely appears in Jira tickets or performance reviews. Research suggests up to 50% of technical work is invisible to at least one stakeholder, and teams may spend 40% of their time on unrecorded tasks. Developers who absorb too much glue work risk career stagnation and burnout, while organizations that ignore it accumulate technical debt and hidden capacity loss. The post covers how to shift from 'accidental' to 'intentional' glue through brag documents, reframed communication, async written records, and organizational practices like refactoring budgets, wins channels, and rotational roles. It also surveys engineering analytics tools (Swarmia, LinearB, DX) and AI-assisted PR review tools (CodeRabbit, GitHub Copilot) that can surface invisible contributions automatically. A practical audit checklist and retrospective questions are included for engineering managers.