GP posting "Everyone I personally know working in software stopped writing code" on HN is such an obvious tell of blinkered delusion.
Literally all HN talks about is AI these days, and it is very, very clear that plenty of people are still writing lots of code, many finding AI makes them slower and causes more problems, and many making the reverse claims. There is always a rich mix of opinions and experiences here.
You would have to believe that literally everyone on HN is a bot (and also everyone on Reddit, Twitter, astralcodexten, or anywhere else online) to discount all these differing opinions in favor of "everyone I personally know" .
No, that’s not accurate. I’m not sure what to tell you. It’s like hearing that no serious programmer uses Python, it’s so far from my experience and that of everyone I know in the field that I don’t know how to engage.
> I used Claude Code and Codex for the translation. This was human-directed, not autonomous code generation. I decided what to port, in what order, and what the Rust code should look like. It was hundreds of small prompts, steering the agents where things needed to go. After the initial translation, I ran multiple passes of adversarial review, asking different models to analyze the code for mistakes and bad patterns.
Sounds to me like "wrote their code using AI only".
I guess when you have 65k tests you can use an AI for transpiling, and it still seems it took an enormous amount of hand holding. That is very far from actually writing new code. But you tell me, are you a software developer? Write or have code written everyday? I am one and for me and everyone I know AI has been mostly just a (fantastic) replacement for google search.
Literally none of the predictions you listed in your post came true. We don't have reliable agents, AI isn't writing most code, hallucinations still happen all the time, improvement has been basically non-existent. Despite the constant claims of these experts and AI boosters, AI is still not a tool one can use to get meaningful work done.
You're in denial. The great problem with AI coding is now that it does too much, not too little. See the endless stream of vulnerabilities or the constant barrage of vibe coded apps, that get ever more complex.
This is absolutely terrible advice. You should never ever use LLMs to work on something you don't understand already, because you have no way to catch the machine when it screws up (and it will screw up). Just like with every other form of automation before LLMs, a smart person only automates things he already knows how to do himself.
I mostly agree it's an area that's risky to wander into mindlessly but it is much more easier to validate knowledge than to practice it.
E.g. I can't write Chinese but can validate if piece of Chinese is a valid one (by feeding to N translators, other LLMs or asking a friend who knows Chinese).
Under assumption of "LLM output is false until proven otherwise" it's not a bad approach and worked for me in various scenarios. (E.g. I asked for implementation of algorithm in Rust and then validated it against base definition).
Yeah no. Getting the first hello world up is more important than anything else.
Until you physically see it running learning is slow.
I learned k8s through many months of study and pain pre AI. Once I actually got it up learning was FAR easier.
This is like using a jupyter notebook to learn python and is always the first thing I point to for someone just starting to learn. Only after should you learn venv, pip install, classes ect.
100% use AI to get started on something you don't understand. I will literally never start to learn about a technical system again without first doing a hello world with AI.
LLMs are pretty bad at writing those things in my experience. They will invent HCL syntax that doesn't exist, generate absurdly overwrought Helm charts, put in assumptions that don't make any sense, and so on. It's faster, and better quality, to write the stuff myself.
> I love computers too, but it doesn't resonate with me when people call AI "snake oil." The comparison suggests that the thing doesn't do what it's marketed to do.
Well yeah, because it doesn't. AI is being claimed to be a magical genius intelligence which will solve everything forever, but in reality LLMs are still idiots you can't trust to not screw up without a tight leash. They can't even do the one thing they are supposed to be good at (programming) well, despite all the effort which has been focused on trying to make them good at it. They don't remotely do what they are marketed to do, not even close!
> We didn't have a far-right Hitler or a far-left Stalin because we had a Roosevelt. We should aim for that again...
I would much rather not have a repeat of the president who ran the federal government like he was a king, and the Constitution a bare semblance of a suggestion. FDR was one of the worst presidents in history, and many of the problems we face in our country today can be traced back to his immense executive branch power grab.
That's a very lackluster argument. Even if everything you said was true (and to be clear: it absolutely isn't; LLMs will hallucinate no matter what as it's in their very nature), that's still a flaw in the tool. A good tool must not require convoluted dances to make it work halfway decently.
AI code assistants are lazy junior developers (so you need to keep an eye on everything they do, e.g. make sure they don't forget or ignore to do some parts of the work you tell them to do) with the ability to do research as in-depth as a senior developer. Now make your mind about it. When driving an AI code assistant, you must act like you are a softare development manager managing a team of junior developers.
Because they feel (rightly or wrongly) there is no viable alternative. It might be that they have software which requires Windows, it might be that they think it's too complicated to set up Linux, or it might just be that they aren't aware any other option exists. But those all boil down to the same thing: people think they have to use Windows, so they tolerate its nonsense.
Yes, that was removed with the 64-bit versions of Windows. My understanding is because they were using a compatibility layer to run 16-bit apps, and with 64-bit Windows they changed that compatibility layer to run 32-bit apps. But I'm not a Windows internals expert so I could be mistaken.
Then you are dead wrong. Anyone who gives a shit about doing a good job is still writing code.
reply