834 karma · joined October 28, 2021
Most consumer software in developed under the assumption that features only have a cost when being built. Their maintenance cost, and the combinatorial complexity each new feature adds, is barely considered. As a result, software teams add complexity at a speed that exceeds the rate at which the team's size, and the volume of work it can handle, grows. Eventually this reaches a critical threshold and the quality of the software starts to decline. But this doesn't mean the software couldn't still be improved, just that there isn't the resource available to do so.
Nor can you just keep it quiet and smuggle it out in a regular release as you suggest. For one thing, changes in important software are be linked to commits and have pull requests, reviews, etc. Changes without these will immediately raise suspicion, as either a malicious change snuck into a release, or as a "quiet" fix to a major vulnerability, completely undermining the purpose of keeping it quiet in the first place. Moreover, major vulnerability fixes cannot be "quiet", because the whole point is to get as many people as possible to upgrade as quickly as possible. If PHP (or whoever) push out a release containing a major security fix, but don't make this clear, then many people will be in no rush to upgrade, and will get pwned.
https://blog.jetbrains.com/research/2026/08/ai-coding-agent-...
"90% of professional developers were using AI coding agents at work at least weekly in one form or another (local agents or remote cloud agents), with 68% using them daily."
Re. context:
"The Developer Ecosystem and AI Pulse surveys are localized into eight languages: English, Spanish, Chinese, Japanese, Korean, German, French, and Portuguese. We apply quotas on the required number of responses by region to help achieve accurate global representation. ... The Developer Ecosystem Survey has been statistically reweighted to better represent the global developer population by region, employment status, programming language, and familiarity with JetBrains products"
Here is one of his posts from 2022:
"Since a long time now I was interested in learning computer graphics and “do stuff” with computer graphics APIs. I began to work on a very simple Game engine in Swift / Metal last year but I began to switch to a Windows machine a few months ago, and Swift / Metal is not compatible with Windows (and will never be I think)."
https://carette.xyz/posts/opengl_and_cpp_on_m1_mac/
This is the same person who is apparently now writing:
"It is a transaction where you sell the part of you that was supposed to care. Do that often enough, and it does not come back. That is not burnout, but it is still a disease. Although, like every disease, it spreads: first to your team, then to your product, then to the people using it."
[1] https://openai.com/index/research-acceleration-view-inside-o... [2] https://openai.com/index/an-alien-mind/
https://azure.microsoft.com/en-us/updates?filters=%5B%22Azur...
That's not necessarily a bad thing for stability, but long-term I would not be surprised if it gets EOL-ed, or radically shrunk to just a basic Git mirroring service.
Ironically, the author would have been better asking an LLM to write the article. At least it would have found better sources and developed more convincing arguments.
It takes years or decades for the automation of an artisan process to shake out, because it involves rethinking how everything around the now-automated process happens, and because the benefits involve the automation's ability to continue scaling beyond a level where human capacity was saturated. We're only at the very beginning of that process for coding, and right now we tend to see LLMs somewhat awkwardly inserted into pre-existing software development lifecycles. But it's unlikely that'll be still be the way we're creating software in 10/20 years time.
Of course, it's not a perfect system, but it tends to avoid the excesses of control, violence and oppression that other power structures can enable. I try to avoid employers, clubs and other organisations whose internal dynamics don't resemble it (aside from the killing). As a result, I've mostly avoided the kind of stress and politics that other people seem to find themselves mired in.
He didn't make compute deals until he saw the growth necessary to justify them. As a result, they're paying over-the-odds compared to if they'd have make deals earlier. Maybe that was a poor business decision, but I'm not sure how it represents speaking out of "both sides of his mouth"? Sounds like he was honest.
> An asm.js module can take up to three optional parameters, providing access to external JavaScript code and data:
> - a standard library object, providing access to a limited subset of the JavaScript standard libraries;
> - a foreign function interface (FFI), providing access to custom external JavaScript functions; and
> - a heap buffer, providing a single ArrayBuffer to act as the asm.js heap.
From http://asmjs.org/spec/latest/#introduction:~:text=External%2...