一切都无法运转,但每个人都欣喜若狂。
If coding has been solved, why does software keep getting worse?

原始链接: https://ptrchm.com/posts/nothing-works-and-everyone-is-euphoric/

科技行业目前正深陷于由人工智能引发的狂热之中,各大公司竞相利用新型模型来提高生产力和产出。然而,尽管拥有这些强大的工具,现代软件的质量却在直线下降。从反应迟钝的汽车界面到频繁崩溃的银行应用,数字体验正变得日益脆弱且令人沮丧。 作者认为,这种衰退源于一种痴迷于“功能驱动型关键绩效指标(KPI)”而非稳定性的文化。由于“修复漏洞”在管理层的演示报告中并不亮眼,复杂性的增长已经超过了质量的提升,导致了系统臃肿和技术债务。虽然传统软件并非完美,但它们更为简洁;而如今对无尽抽象层的依赖,使得更新成为了恐惧而非进步的来源。 尽管如此,作者对未来仍持乐观态度。虽然大型企业继续沉溺于“人工智能债务”中,但独立开发者现在拥有了构建更好、更可靠替代品的超能力。大众对当前软件的普遍不满正在酝酿一场“反叛”,这将为由那些优先考虑用户体验而非企业指标的人所开发的新一代高质量工具铺平道路。

这次讨论反映了一个广泛的共识:软件质量正在下降,其特征是功能臃肿、“垃圾化”(enshittification)以及用户自主权的普遍缺失。参与者认为,软件设计的初衷日益倾向于股东利益和“用户粘性”指标,而非最终用户的需求。 共识指出几个关键驱动因素: * **激励机制错位:** 组织优先考虑发布“亮眼”的新功能以证明增长并维持管理层的职位,而不是专注于稳定性、用户体验或修复长期存在的漏洞。 * **组织衰退:** 软件生命周期往往由非技术背景的产品经理和官僚流程主导,这些流程偏好“快乐路径”的最小可行性产品(MVP),而非稳健的工程实践。 * **AI 作为加速器:** 虽然人工智能并非根本原因,但它充当了“垃圾化”工具,促成了“劣质内容”的快速生产——即那些编写迅速,却缺乏工艺、深度测试或可靠软件所需架构完整性的代码。 * **自主权丧失:** 用户感到被困在某些生态系统(如 macOS 或 Windows)中,这些系统优先考虑控制权和遥测数据,而非提供一个透明、可修复的环境。 许多参与者建议,唯一真正的“补救措施”是回归简约,专注于“有见地”的软件,或转向尊重用户的开源替代方案。
相关文章

原文

As I’m writing this, we’re in the middle of an AI-induced mass psychosis. People are literally token-maxxing themselves into hospital beds, scrambling to capture some of that market value before everything is automated away. I can’t blame them. Models keep getting better, programmers are being laid off left and right. We’ve been repeatedly told that AI will write 100% of the code by the end of the year. Whether that’s true or not, this may not be the best time to sit back.

The widespread excitement around the Agentic Era comes with the promise of greater productivity and higher quality. There’s no denying that these new tools have already revolutionized how we create and use software. They have raised upper management’s expectations for team output. They may have upgraded the average skill set of software teams in a way we have not seen before.

So why does software keep getting worse across the board?

A few examples from last week alone:

  • My banking app requires, on average, three FaceID logins before the 3D Secure confirmation view appears.
  • I opened Slack on macOS, the icon kept bouncing in the dock for a few seconds. I got impatient, switched to Ghostty, and started typing. Just then, the Slack window appeared, stole focus from Ghostty and the git pull command was sent to the group chat.
  • My LG fridge started making weird sounds, so I tried to file a warranty claim, through a multi-step form with countless fields. It failed with a submission error at the very end. And I only found out because I looked at the JavaScript console.
  • My car’s infotainment system got a software update recently. It was never great to begin with, but at least it didn’t reboot itself during every drive. Now, it’s riddled with bugs: the turn-signal sound randomly goes silent until I reboot the OS; I tap the screen to open Google Maps – the radio app shows up; there’s a 1-2-second lag before anything happens after I tap the screen. This is no longer just a UX problem at this point – those bugs affect your ability to focus on driving.

    A few months ago, I saw a LinkedIn thread by a PM on the team that redesigned the car’s OS. They were congratulating themselves on what an amazing job they had done. I keep thinking about that post every time I have to fight their product.

While I can’t know the full story, I’m willing to bet that most of the teams behind those bugs have access to the latest models, with generous token budgets. LLMs can be really good at squashing bugs if given the chance.

Software has always had bugs, and the nostalgia for the good old macOS Snow Leopard era when everything was stable is mostly the product of selective memory. Software may have been better back in the day, but that was mainly because it was much simpler. Since then, we have kept coming up with new abstractions, new frontend frameworks, and more infrastructure complexity. The bar for “user experience” has kept rising, but everything has become increasingly fragile.

We’ve reached a point where an update to macOS – or to any app I rely on, really – is a source of dread rather than excitement. I now expect the new version to be worse.

This isn’t a rant against AI. Those humming GPU farms have given us superpowers, but we still can’t use them to build better software.

Software vendors have long been KPI-oriented, and making things more stable doesn’t always have a direct effect on the numbers. It doesn’t look exciting in presentations:

This quarter, we won’t be releasing any new features, and we have no plans to redesign anything — we will exclusively focus on fixing bugs.

— Imaginary PM at a BigCo

Until this attitude changes, the great software quality decay will continue.

That doesn’t sound optimistic, but I’m actually excited about what comes next. As companies collectively spiral into AI debt, individual developers have a unique opportunity to build software that would previously have been beyond their reach.

I have no hope for my car’s Android Auto or LG’s stupid website – but I choose to believe that everyday software will get better as a result of this frustration. We’re already seeing acts of rebellion against the current state of macOS and Windows, and I hope the trend will spread across the stack.

联系我们 contact @ memedata.com