‘I’m proud of being a job hopper’: Seattle engineer’s post about company loyalty goes viral::undefined

  • Odelay42@lemmy.world
    link
    fedilink
    English
    arrow-up
    186
    arrow-down
    6
    ·
    8 months ago

    Most people over-index on maximizing compensation or holding on to stability. But there’s more to work than money and stability. Work is about growth, building connections, working on things you care about, being challenged and creating a legacy.

    Fucking legacy? Is this a joke? Who gives a shit about what shitty products they launch for FAANG companies? I certainly don’t - not beyond keeping my resume and portfolio up to date.

    Compensation and stability are the only things that matter beyond basic working conditions and a non-toxic environment.

    • rockSlayer@lemmy.world
      link
      fedilink
      English
      arrow-up
      83
      arrow-down
      2
      ·
      7 months ago

      Well in my case I created a legacy by helping to unionize my workplace. I don’t even care if I’m ever remembered for that, not many legacies can be beat

    • Static_Rocket@lemmy.world
      link
      fedilink
      English
      arrow-up
      17
      arrow-down
      3
      ·
      7 months ago

      I don’t know man, I’ve always liked the idea of a project outliving me. Though for the sanity of future engineers I hope that is not the case. Today’s solutions are usually just tomorrow’s problems.

      • nxdefiant@startrek.website
        link
        fedilink
        English
        arrow-up
        17
        ·
        edit-2
        7 months ago

        On a long enough timeline, all things end, and tech has hyper accelerated timelines.

        I was once interviewed by a guy who asked for my biggest failure, which was basically “favorite open source project didn’t work out”. He let me know he worked on an early competitor of the X windowing system and really believed in it. And we laughed about that. (He hired me).

        So yeah, I kinda agree with this job hopper guy on everything but legacy, but only because we really don’t get to have a say on what our code ends up meaning to anyone. The sands of time are nothing compared to the brutality of tech stack churn.

    • PhAzE@lemmy.ca
      link
      fedilink
      English
      arrow-up
      12
      ·
      7 months ago

      Who invented Google home? Like, what’s the person’s name? What about the person that designed the Sonos Move?

      There’s no legacy. There’s business objectives and getting those completed so upper management can move their plans forward. Who gets them there is irrelevant.

    • fidodo@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      ·
      7 months ago

      Seriously, nobody is going to remember you. Like 3 generations down, you’ll even be a tiny blip in your descendents world. Even most billionaires will be remembered through an encyclopedia entry and nothing else.

    • stealth_cookies@lemmy.ca
      link
      fedilink
      English
      arrow-up
      2
      ·
      7 months ago

      Agreed, something has gone wrong if I individually am so important that what I leave at a job is considered a legacy.

      All I want is for the things I work on to be useful for the lifetime of the product and some appreciation from management for putting in the work while getting paid well.