‹ BackHN Continuity

Thread

Doing Everyone Else's Job

215 points · 115 comments · luu

  1. dmurray · · focus · HN ↗
    One of the things I hate about my current job is that it's impossible to do this.

    Everything is locked behind multiple layers of permissions. It takes weeks to get the correct permissions set up even for my actual job (which I see any time changing roles here, or when onboarding new hires). Getting the permissions to jump in and improve some other part of the system that I don't officially own - even though I might get granted them if I ask nicely, because nobody knows who is actually meant to have what permissions - is so much higher friction than asking the "right" person.

    1. LtWorf · · focus · HN ↗
      I worked at a company where you could do it, but some people take fixes as insults to their mother's honour, so all in all probably on a personal level it is best to avoid doing it.
      1. HolyLampshade · · focus · HN ↗
        I’ve only worked in a single company where it really worked out, and it took a massive amount of work to massage egos on both sides of the “fix” (one side sees their hammer tool and wants to fix everything with it, and the other has the mother’s honor issue). You really had to spend time with both parties helping them understand things were a certain way for a reason, but that there were always small changes that could improve things.

        Encouraging the inverse of fixing relationship helped both parties as well.

        That said, I’ve worked in a few other shops that either had the permissions/compartmentalization shit show as a permanent blocker, or were just completely devoid of a culture encouraging people to care about anything beyond their own career/fiefdom. I absolutely despise both cases.

      2. moomoo11 · · focus · HN ↗
        such companies deserve to fail and the most honorable thing you can do is find another job or start a competitor.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.