Also interesting the top entry is from fabrice bellard: https://bellard.org/nncp/nncp.pdf
177 karma · joined September 18, 2019
Also interesting the top entry is from fabrice bellard: https://bellard.org/nncp/nncp.pdf
This is worthy feedback to the author (and others), that writing with clear AI tells/register is so distracting that it takes away from the spirit and content of the writing.
Perhaps this is just the zeitgeist and in 20 years this is irrelevant. It’s relevant for whoever is writing now.
I know you're being downvoted, because people are tired of hearing "this is AI".
But I think your comment "this is AI" is warranted. This content, explaining something of cultural, personal significance (instead of the typical technical explainer) should really be written by a human.
You're lucky to be in a system that works out for you. Not everyone is in such a lucky position. LLMs help automate the tedium out of their job, and hopefully, have a bit more extra energy to make a better system within their immediate locus of control.
In contrast if you ask GPT 5.5/5.6 to speak directly/plainly, it will just straight up tell you the content "X is right, Y is wrong". Much preferable.
There is so much work out there that is repetitive / boilerplate / tedium. If you get to personally work on interesting work more than 50% of the time (pre-LLM) I'd say your job is #blessed.
If you could access the current models as base models I guess you'd still get very interesting hilarious stuff.
If we think about that as the intended competition (and not websites corps spent millions on design/polish/copy), I'd argue that AI (model + coding agent + skills + whatever) is doing a better job overall. Most agencies don't spend enough effort in understanding what you want, or hire juniors and bill them as seniors. It's almost always late, overbilled, somewhat what you said you wanted but not really, and technically terrible.
I've experienced enough business-critical incidents (or requests) where people across all seniority are just randomly trying stuff, making a mess, without taking time to coordinate, understand the problem, and solve it. It almost always resulted in more overall time and bigger blast radius than if we did it not out of panick.
OTOH my "slow" (I still did things fast, just not purely for the sake of looking fast) and steady approach always took me less time overall to find a proper fix. I also became known as the person who could always find the best possible fix when there's an incident/time constraint, but I also thought that was systematically bad instead of fixing the culture/process.
It's still faster to take a minute (and deep breath), understand the whole problem (incl. urgency and how that affects your solutions), and then solve it. It doesn't mean you can't keep your customers in the loop and assuage their concerns.
If you add a score/metric this incentivizes the wrong thing, like how money, funding, and career already incentivizes all the wrong non-scientific behaviors (like faking data, p-hacking, etc.)
Humans at the moment are still better at building on our own knowledge and compounding our effort:output ratio, due to our superior plasticity. See https://joyemang33.github.io/blog/2026/humans-dont-just-samp... for a small experiment. That's why for programmers experienced with a particular language/codebase/domain, it feels like minimal effort to know where and what to change. "Why use LLMs when I can do it in 10 minutes"?
Of course, relying on our long term memory instead of re-ingesting the code, is also a problem for having assumptions that don't get updated, e.g. revisiting a codebase that's been updated by many others. With the rate of change/churn of codebases I'm wondering if this is naturally forcing us to use AI anyways, since it's really hard to keep track of a lot of code changes by AI as a human. Once you start down the path of not reading code yourself, the friction to start reading code gets higher in a feedback loop. I know people (incl. myself) who are still reading code in their own coding/agent sessions, but that's unsustainable in an organizational setting - you won't be able to ingest N'0,000s of LoC of changes every week if there is no incentive to do so.
Is that a good thing? It's unlikely LLMs in their current state will be "neuroplastic" for a single person's use case (mostly market reasons - cost of owning, running, tuning models will likely be unattainable for the foreseeable future). In a few generations, this would be a total surrender of all foundational coding to LLMs (unsure about knowledge work in other domains). Will text files with superintelligent models be enough to encode long term and broad understanding of a domain? Is it necessary if a model is superintelligent? What if a person/nation/species loses access to LLMs through supernatural / political reasons at that point? Will it be like losing the last remaining COBOL programmers to your mainframe? I'm sure we're resilient enough to re-learn all of that, but it will be a huge crutch like never before.
All that to say, it's still worth learning programming, and doing some things by hand, even if it's not "economically valuable" (at least on the surface). Even with web frameworks, it's still worth manually plumbing between frontend/backend/database. Even with interpreters and compilers, it is still worth understanding and doing a bit of assembly. Even with assemblers, it's still worth understanding machine code, CPU and architecture quirks. It's worth looking at the historical artifacts (both senses of the word) and understanding intents, constraints, and creativity (as another comment [1] has more beautifully said).
Two "further than programming" courses that also embody the spirit of the article (get interested, hands-on, play) have been impactful on my appreciation of computing systems are nand2tetris [2] and OS in 1000 lines [3]. Both are "easy" in the sense that they make certain design decisions so you don't have to dig through thousands of pages of manuals. If you wish, during or after the process, you can explore specific concepts further. It's broken down in the right pieces and checkpoints, so you get quick feedback on whether something is working or not. It's still very much a puzzle you have to solve, but the right difficulty/complexity ladder (great instructional design).
[1] https://news.ycombinator.com/item?id=49093468 [2] https://www.nand2tetris.org/ [3] https://operating-system-in-1000-lines.vercel.app/en/
I think that was Nolan's intent all along - a very Nolan, American/Hollywood take on the Odyssey.
Edit: FWIW the paper the post quoted has repositories as slop baseline https://arxiv.org/html/2603.24755v1#S4.SS2
Open weight AI is decelerationist from the perspective that all capital should be allocated to a market leaders for training, and that the market leader is fully invested in continuously making the models smarter, cheaper, faster for its users, or that distillation from this market leader is the main way to make progress.
We might reach a local optimum/equilibrium faster without open weight models, with leaders capturing more of the market faster to a point where further R&D isn't required due to lack of competition. I also doubt that distillation is the only/main way that open weight models were advancing AI research. We can name a few examples from DeepSeek around reasoning, context optimization, etc. I'm also unconvinced that the overall market capex on AI is lower given more competition (probably less specifically for US market capex, which is decelerationist from only the US perspective).
Even if it doesn't fit in the context window, the model can search through past turns and sanity check if something doesn't seem to be going right, or be prompted to follow an early message, "when starting on a new item, review the first message for how we should approach this"
Overall, seems like it got more nuanced over time - even though it's still broadly in favor of SQL. Favor for ORMs (flagged also as a term that can mean many things to different people) is more in terms of type safety, mapping, migrations, etc. so more a library/utility rather than a framework that fully abstracts away the database.
Fully agreed. Though I found that, once I found a harness (prompt + skills + model) that I trust to do most things the way I like it, it has sped up the coding/exploration part of that process.
Although the iterations are faster, it's still taking me almost the same amount of effort to go through those crappy versions, because I still need to understand and adjust my mental model of what ideas, principles, design apply for the solution, and what to try next.
So, in the end, I do feel like I'm expending more mental effort in a shorter amount of time (with some effort saved on writing the code, which wasn't that much to begin with once you're proficient). It's a weird feeling, like I'm "only" prompting and reading code, but I feel equally mentally spent, or sometimes more because of the compressed iteration cycle.
I'm generally an optimistic person and very trusting of others. I'd say I'm also a pretty good reader of intentions / listener based on people who are my friends / worked with me (anecdotal of course, take it how you will).
However, some of the comments in the GitHub issue... I can only assume the worst of intentions to ruin any/all motivation of the maintainer. Given we've seen social engineering and other attacks on other open source projects with increasing frequency, I can only assume that there are ulterior motives in such comments.
I cannot otherwise see how those comments would be constructive towards the maintainer or the other participants in the issue.
Even on 1080p videos running on AV1 on 1x, the TV system bogs down and any kind of interaction has a variable 1-3s lag. On some TVs if you do 1.25x the TV automatically "downgrades" the resolution to 480p to avoid dropping frames.
I wish there was an option to still use VP9 / H.264 on those systems (even limited to 1080p).
- a response to my comment saying that I am "illiterate" and cannot differentiate LLM output vs actual human comments (in that case I'm not sure what you're adding to the discussion here beyond a personal attack)
- a general comment saying it's getting harder for people in a position similar to us (i.e. tech / tech-adjacent who interact a lot with others who write with LLM assistance or via LLMs) to differentiate human/AI output.
I'll assume good faith and you mean the second. In that case maybe you can explain the "fundamental problem" you're referring to?