‹ BackHN Continuity

Thread

A Staff Engineer's Guide to Inventing Work

380 points · 93 comments · amortize

  1. fsloth · · focus · HN ↗
    "that work does not exist unless an engineer invents it."

    This is so strange. To my mind the only purpose companies hire engineers is to support business. The staff engineer should not need a project manager to tell what is interesting for business aspects - even though the goals are likely mostly technical.

    I do realize this does not hold up always. But to me if you can't provide some reasoning for your work in business metrics you are participating in an academic exercise.

    1. devmor · · focus · HN ↗
      I think you're operating on a different definition of "work".

      The OP is discussing tasks to do, you sound like you are discussing things that need to be done. The OP isn't saying there aren't things to be done, they are saying that no one is going to tell them what needs to be done, so they must discover and formalize it.

      "Inventing Work" is a bit tongue-in-cheek.

    2. OtherShrezzing · · focus · HN ↗
      >To my mind the only purpose companies hire engineers is to support business.

      Lots of hires, especially in places big enough to have dedicated teams for platform work, are for empire building, rather than to support business needs. In these situations, companies hire engineers because a higher-level manager needs to increase their headcount, in order to pad out their CV for their next move.

      [0] <a href="https:&#x2F;&#x2F;www.investopedia.com&#x2F;terms&#x2F;e&#x2F;empirebuilding.asp" rel="nofollow">https:&#x2F;&#x2F;www.investopedia.com&#x2F;terms&#x2F;e&#x2F;empirebuilding.asp

      1. merrvk · · focus · HN ↗
        Absolutely spot on.The time main output is unnecessary busywork that is purely designed to pad out CV’s
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.