Comment on What's the dumbest thing you've shipped?

lauha@lemmy.one ⁨1⁩ ⁨year⁩ ago

• aport@programming.dev ⁨1⁩ ⁨year⁩ ago

  On the plus side no users means no bug reports or feature requests

  source

  • PoisonedPrisonPanda@discuss.tchncs.de ⁨1⁩ ⁨year⁩ ago

    whistles

    Always look on the bright side of life…

    source
  • idunnololz@lemmy.world ⁨1⁩ ⁨year⁩ ago

    And you get paid for it regardless. It’s win-win :D

    source

    • TCB13@lemmy.world ⁨1⁩ ⁨year⁩ ago

      Yeah, no optimization / quality required ahah

      source
  • lauha@lemmy.one ⁨1⁩ ⁨year⁩ ago

    Nice

    source
  • realitista@lemm.ee ⁨1⁩ ⁨year⁩ ago

    youtu.be/SJUhlRoBL8M?si=3FIN6W-f_9yOWmnk

    source
• lemmyvore@feddit.nl ⁨1⁩ ⁨year⁩ ago

  I think of it like a rite of passage nowadays. I remember how badly it would affect me when I started out and I can see how hard it hits juniors and mid-levei developers nowadays, it’s one of the biggest threats to morale in a team.

  source

  • snuff@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Ot fucking sucks because I watched this whole train wreck play out in slow motion.

    We told our managers from the beginning it was a waste of time and that we should focus on the more important project that will depreciate this one anyway.

    I built the tool they wanted, within the constraints of our corporate network configuration, and it worked really well. But it required the customer to change one thing about their workflow, which would require certification.

    So they slowly scoped it back and back until it does basically nothing.

    But even though the app does nothing and has no users, I still had to generate all the documents and artifacts and recovery plans etc. I wish sometimes that I would have gotten my degree in civil engineering or something more real.

    source
• peter@feddit.uk ⁨1⁩ ⁨year⁩ ago

  Or knowing that what you’re working on is going to be scrapped before completion

  source