How dare I polish and remove kludges from previous releases. 😆

Also, none of those kludges would have even been necessary if the project scope was properly defined from the start and the project manager didn’t let the users keep trickling in new requirements without also extending the deadline.

So yeah, how dare I go back and implement something the way it should have been done the first time?

  • Captain Aggravated@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 months ago

    Software developers are uniquely arrogant in their belief that they have a right to choose when the workers of entire industries or sometimes everyone in the world needs to re-train on the tools they use to do their jobs.

    I’m a woodworker. Imagine if I walked into the shop one day to find my table saw replaced with one of those mutant sliding table European things because the manufacturer pushed an update. “We’ve replaced your tool with one that conforms to recently adopted industry norms, buzzwords and trendy design patterns we in the table saw industry have been peer pressuring each other into adopting. You may proceed to suckle upon our genitals in gratitude and worship.”

    Meanwhile I’m losing money because the tool I rely on to run my business no longer functions how I was trained to use it. I have to tell my customers that their orders aren’t getting filled because I was visited by the saw fairy and instead of building their furniture for them I have to read manuals, learn how to safely use this thing, find where all the controls went, and then remake all the jigs and tooling I relied on for production and hopefully I can get back to doing actual work before they change it again according to their needs and not mine, on their schedule and not mine.

    That’s what it’s like using software in the age of nightly updates or worse cloud-based solutions. You never know when your tools will change out from under you mid-project.