Software has a problem. OK, it has many problems. I've already highlighted one of them. But this is another important one. The pr...

Software has a problem.

OK, it has many problems. I’ve already highlighted one of them. But this is another important one.

The problem is that software—all software, with no exceptions—sucks. The reason for this is multifaceted and we could spend years and years arguing about who has the larger list of reasons, but in the end it boils down to the proverbial shoemaker’s children: Our development tools are the worst of the worst in software.

  • sparseMatrix
    0•2 years ago

    Many use cases, many hats. Most of us play multiple roles in our lives, whether we know it or not – and so wear multiple hats.

    We’re all victims, to a degree, of poor software design, and we’re all responsible for it to a degree as well. If for no other reason, because we make some compromise for some other perceived gain. We literally enable bad software every time we use it.

    Thinking of you here, Google, and your compatriots Facebook and Twitter.

    Not just to be argumentative, but rather to suggest that there is something we can all do about it. Even those among us who are not programmers or engineers can raise awareness among both other users and service/software providers, and refuse to use bad software and crappy insecure web technology.

    • @[email protected]OP
      0•2 years ago

      One thing we can all do (users and practitioners both) is STOP ACCEPTING EXCUSES. Buggy software is broken software. Period. Shove this in the practitioners’ faces (and accept that it will be shoved into ours!) and stop standing for it.

      One of the reasons we in this industry have gotten into this state is that we’ve convinced the public (and ourselves) that this is normal. We’ve shot ourselves in the foot for so often that we think walking around leaving bloody footprints behind is normal.

      And we’re about the only branch of “engineering” (scare quotes because I can count on one hand the number of software makers I think use engineering principles–and I don’t number myself on that hand) that tolerates the kind of cowboy bullshit that is normal. Cowboy civil engineers get sued to perdition and/or jailed when their output is fundamentally broken. When mechanical engineers make broken shit, they go bankrupt from the returns. Yet when software “engineers” product total and absolute shit they get away scot free and, indeed, they often, bizarrely, manage to sell the repairs as “new software”.