• Doc Avid Mornington@midwest.socialEnglish
    48·
    9 months ago

    Or gets promoted, and keeps moving on to new and bigger projects, leaving a trail of destruction, because all management sees is they close tickets faster than the people who are busy picking up the pieces behind them.

    • OpenPassageways@lemmy.zip
      11·
      9 months ago

      In addition, the company doesn’t invest in growing and retaining the rest of the development team for 20 years until said developer is near retirement, then finds that they need to hire 10 developers because 2 need to replace said person and 8 need to redo everything they did.

  • Sabre363@sh.itjust.worksEnglish
    25·
    9 months ago

    I sorta did this at my old factory job by setting up all the machines to run damn near perfectly then I peaced out before showing anyone how to actually run the set-ups.

    • ☆ Yσɠƚԋσʂ ☆@lemmy.mlOP
      262·
      9 months ago

      I managed to do this on my very first job. I worked at a company where they needed to integrate data from multiple vendors into a unified schema. So, ended up building a library that could take xpath and a value and would navigate down the the path, creating missing entries along the way, then insert the value at the given location. It worked really nicely cause it let our business people just fill out a spreadsheet, and provide a csv that would get ingested. The internals of it were absolutely nightmarish though, cause I just kept kludging stuff in to accommodate for new use cases, and of course all of it was completely undocumented. After I left, I heard that at least three separate attempts were made at rewriting that nightmare, and everyone just gave up eventually. For all I know, it’s still in production to this day because it became a foundational piece that nobody has any hope of understanding. 😂

  • davel@lemmy.mlEnglish
    18·
    9 months ago

    Perfect re-entry: Contracts at same company to maintain same code at 3x salary.