I think in this text, details lile the timeline are simplified bit too much. But I agree with the general tendency described.

There was never a time where software was perfect, but the accelerating cadence of serious, widespread incidents with real-world effects seems real.

  • corsicanguppy@lemmy.ca
    link
    fedilink
    English
    arrow-up
    9
    ·
    2 hours ago

    This guy is delightfully close to a cause, but not really.

    In the enterprise space, we largely avoid NPM or Composer, et al, because those very best-practice docs (iso27002, here, later SLSA) prohibit repos that obscure or frustrate validation and code pedigree; and the gleeful incestuous inclusion of projects within projects means source code isn’t properly managed - a failure - so npm won’t do. SBoM and validation is key.

    So that covers half his premise; and while some shops or people use and love npm and cpan et al, the kind of people maintaining banking or travel systems should most absofuckinglutely NOT be using those ecosystems lest they lose their certification the first time a clued audit comes through. You wouldn’t accept code violations from your architect or your builders, and programmers are the same way in that space.

    The problem, it seems, is sloppy people doing sloppy things and not getting caught.

    I’m sure Ai is a big help with this, but it’s only enabled by the same sloppiness that was already present.

    Great news: civil courtrooms try negligence and code-violation cases all the time.

    • solrize@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 hour ago

      SBoM and validation is key.

      Yes, unfortunately the SBoM too often is a Yaml file that gets changed every time someone wants to use a new Ruby gem. https://openssf.org/projects/slsa/ is a page with a small blurb and an embedded video! slsa.dev looks interesting and I’ll check into it later.

      Management everywhere cares about velocity more than they care about anything else. They’ll always find workarounds for anything requiring careful thought.

  • [object Object]@lemmy.ca
    link
    fedilink
    English
    arrow-up
    74
    ·
    edit-2
    3 hours ago

    MBAs and Covid hires are running software into the ground.

    We built a whole KPI and promo system (and reinforcement loop) on “impact” and “velocity” and “commit counts” and layoff threats, and now we’re confused why software is going to shit.

    We built an entire enshittification feedback loop. Of course it’s going to shit! I get paid for what I shop, not what outages I prevented. Oh, we built up blameless retros, but what’s the first thing everyone asks after an outage? At least now we can say Claude did it so we’re not in the hot seat when I stop reviewing PRs, right?

    Jesus fuck.

    ETA: this is a reinforcement loop to produce bad software, externalize as much as possible, and fuck over the user. No wonder everyone hates tech now.

      • [object Object]@lemmy.ca
        link
        fedilink
        English
        arrow-up
        4
        ·
        2 hours ago

        Interesting, hadn’t seen that

        I’ll add there’s a counterpoint to this: if you look at people with a tenure less than 1-2 years at like 4-6 different jobs then you should also be suspicious, because that’s just long enough that they never face consequences for the long term effects of their work.

      • [object Object]@lemmy.ca
        link
        fedilink
        English
        arrow-up
        24
        arrow-down
        1
        ·
        3 hours ago

        Much like I think anyone with a political science degree probably shouldn’t be in politics, I find most MBAs have all been forced to learn the same type of management and it’s terrible.

        • tburkhol@lemmy.world
          link
          fedilink
          English
          arrow-up
          25
          ·
          3 hours ago

          Watched a youtube with the kicker “The degree that destroyed reliability” or some such - MBAs, of course - that was mostly a documentary about Boeing and how changing from engineering CEOs to MBA CEOs literally killed people and nearly destroyed the company.

    • Canaconda@lemmy.ca
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      2
      ·
      3 hours ago

      Buad is such a joke. Everything valuable is in the 1st year. Only someone without a single entrepreneurial bone in their body would finish a degree.

      I remember working for a company in a tech incubator and realizing that literally the incubator’s entire staff were 22 year olds with zero real world experience.

  • jtrek@startrek.website
    link
    fedilink
    English
    arrow-up
    6
    ·
    2 hours ago

    This changed the balance of power between workers and management.

    Imagine a building site where there is a plumber, a builder, and an electrician. If any one of them threatens to quit, you have a problem, because you need each of them to get the project done. Whereas if you can make everyone a mix of plumber-builder-electrician, they lose that leverage.

    Whether you think that power imbalance is a bad thing may depend on your politics. But it had a slow effect of taking influence away from the people close to the work. They’re the ones able to raise the alarm when things start going wrong.

    Another angle on how capitalism is making the world worse. Idiots and incompetents with money are calling the shots, and driving us all off a cliff.

  • xxce2AAb@feddit.dk
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 hours ago

    Yup, we’re all right royally fucked in the least loving way imaginable. Most people just don’t know it yet.

    But they will.