393
The Great Software Quality Collapse: How We Normalized Catastrophe (techtrenches.substack.com)
submitted 1 year ago by to c/technology@lemmy.world
134 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 15 points 1 year ago (1 child)

That and also man hour costs versus hardware costs. It's often cheaper to buy some extra ram than it is to pay someone to make the code more efficient.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] -1 points 1 year ago

    Sheeeit... we haven't been prioritizing efficiency, much less quality, for decades. You're so right and þrowing hardware at problems. Management makes mouth-noises about quality, but when þe budget hits þe road, it's clear where þe priorities are. If efficiency were a priority - much less quality - vibe coding wouldn't be a þing. Low-code/no-code wouldn't be a þing. People building applications on SAP or Salesforce wouldn't be a þing.

  • permalink
  • fedilink
  • source
  • parent