Top
Best
New

Posted by bigwheels 1/26/2026

A few random notes from Claude coding quite a bit last few weeks(twitter.com)
https://xcancel.com/karpathy/status/2015883857489522876
911 points | 847 commentspage 3
rubzah 1/28/2026|
The Slopocalypse - an unexpected variant of Gray Goo:

https://en.wikipedia.org/wiki/Gray_goo

AnimalMuppet 1/28/2026||
Well, it may consume the AI environment. Maybe even the internet. It's not going to consume a PC with g++, though (at least if the PC doesn't update g++ any more once g++ starts accepting AI contributions).

There may come a point where having a "survivor machine" with auto-update turned off may be a really good idea.

Applejinx 1/28/2026||
I already do this, in the form of survivor machines made to do initial coding on a retro platform so the result will translate across all possible platforms. Got to, as I'm an Apple coder primarily, so if I want to target older machines I can only do it through a survivor machine: support is always pruned out of Xcode and it would be insane to try and patch it to keep everything in scope.
direwolf20 1/28/2026||
Aslopalypse, a slop ellipse.
toephu2 1/27/2026||
I think in less than a year writing code manually will be akin to doing arithmetic problems by hand. Sure you can still code manually, but it's going to be a lot faster to use an LLM (calculator).
adamddev1 1/27/2026||
People keep using these analogies but I think these are fundamentally different things.

1. hand arithmetic -> using a calculator

2. assembly -> using a high level language

3. writing code -> making an LLM write code

Number 3 does not belong. Number 3 is a fundamentally different leap because it's not based on deterministic logic. You can't depend on an LLM like you can depend on a calculator or a compiler. LLMs are totally different.

Havoc 1/28/2026||
There are definitely parallels though. eg you could swap out your compiler for a different one that produces slightly different assembly. Similarly a LLM may implement things differently…but if it works do we care? Probably no more than when you buy software you don’t care precisely what compiler optimisation were used. The precise deterministicness isn’t a key feature
yojat661 1/28/2026|||
With the llm, it might work or it might not. If it doesn't work, then you have to keep iterating and hand holding it to make it work. Sometimes that process is less optimal than writing the code manually. With a calculator, you can be sure that the first attempt will work. An idiot with a calculator can still produce correct results. An idiot with an llm often cannot outside trivial solutions.
adamddev1 1/28/2026|||
> but if it works so we care?

It often doesn't work. That's the point. A calculator works 100% of the time. A LLM might work 95% of the time, or 80%, or 40%, or 99% depending on what you're doing. This is difference and a key feature.

Havoc 1/28/2026||
I see. I’d call that fragility/reliability rather than deterministic but semantics I suppose.

To me that isn’t a show stopper. Much of the real world works like that. We put very unreliable humans behind the wheel of 2 ton cars. So in a way this is perhaps just programmers aligning with the messy real world?

Perhaps a bit like architects can only model things so far eventually you need to build the thing and deal with the surprises and imperfection of dirt

kypro 1/27/2026|||
I agree, but writing code is so different to calculations that long-term benefits are less clear.

It doesn't matter how good you are at calculations the answer to 2 + 2 is always 4. There are no methods of solving 2 + 2 which could result in you accidentally giving everyone who reads the result of your calculation write access to your entire DB. But there are different ways to code a system even if the UI is the same, and some of these may neglect to consider permissions.

I think a good parallel here would be to imagine that tomorrow we had access to humanoid robots who could do construction work. Would we want them to just go build skyscrapers and bridges and view all construction businesses which didn't embrace the humanoid robots as akin to doing arithmetic by hand?

You could of course argue that there's no problem here so long as trained construction workers are supervising the robots to make sure they're getting tolerances right and doing good welds, but then what happens 10 years down the road when humans haven't built a building in years? If people are not writing code any more then how can people be expected to review AI generated code?

I think the optimistic picture here is that humans just won't be needed in the future. In theory when models are good enough we should be able to trust the AI systems more than humans. But the less optimistic side of me questions a future in which humans no longer do, or even know how to do such fundamental things.

AstroBen 1/28/2026|||
This is true if your calculator sometimes gave the wrong answer and you had to check each time
pron 1/27/2026||
People who just let the agent code for them, how big of a codebase are you working on? How complex (i.e. is it a codebase that junior programmers could write and maintain)?
aixpert 1/28/2026||
rust compiler and redox operating system with modified Qemu for Mac Vulcan metal pipeline ... probably not junior stuff

you might think I'm kidding but Search redox on github, you will find that project and the anonymous contributions

rester324 1/28/2026||
I am curious. What do you want us to see in that github repo?
bojo 1/28/2026||
I've been an EM for the last 10 of my 25 year Software Engineering career. Coding is, frankly, boring to me anymore, even though I enjoyed doing it most of my career. I had this project I wanted to exist in world but couldn't be bothered to get started.

Decided to figure out what this "vibe coding" nonsense is, and now there's a certain level of joy to all of this again. Being able to clearly define everything using markdown contexts before any code is even written has been a great way to brain dump those 25 years of experience and actually watch something sane get produced.

Here are the stats Claude Code gave me:

  Overview                                                                                       
  ┌───────────────┬────────────────────────────┐                                                 
  │    Metric     │           Value            │                                                 
  ├───────────────┼────────────────────────────┤                                                 
  │ Total Commits │ 365                        │                                                 
  ├───────────────┼────────────────────────────┤                                                 
  │ Project Age   │ 7 days (Jan 20 - 27, 2026) │                                                 
  ├───────────────┼────────────────────────────┤                                                 
  │ Open Issues   │ 5                          │                                                 
  ├───────────────┼────────────────────────────┤                                                 
  │ Contributors  │ 1                          │                                                 
  └───────────────┴────────────────────────────┘                                                 
  Lines of Code by Language                                                                      
  ┌───────────────────────────┬───────┬────────┬───────────┐                                     
  │         Language          │ Files │ Lines  │ % of Code │                                     
  ├───────────────────────────┼───────┼────────┼───────────┤                                     
  │ Rust (Backend)            │    94 │ 31,317 │     51.8% │                                     
  ├───────────────────────────┼───────┼────────┼───────────┤                                     
  │ TypeScript/TSX (Frontend) │   189 │ 29,167 │     48.2% │                                     
  ├───────────────────────────┼───────┼────────┼───────────┤                                     
  │ SQL (Migrations)          │    34 │  1,334 │         — │                                     
  ├───────────────────────────┼───────┼────────┼───────────┤                                     
  │ CSS                       │     — │  1,868 │         — │                                     
  ├───────────────────────────┼───────┼────────┼───────────┤                                     
  │ Markdown (Docs)           │    37 │  9,485 │         — │                                     
  ├───────────────────────────┼───────┼────────┼───────────┤                                     
  │ Total Source              │   317 │ 60,484 │      100% │                                     
  └───────────────────────────┴───────┴────────┴───────────┘
bojo 1/28/2026||
In case anyone is curious, here was my epiphany project from 2 weeks ago: https://github.com/boj/the-project

I then realized I could feed it everything it ever needed to know. Just create a docs/* folder and tell it to read that every session.

Through discovery I learned about CLAUDE.md, and adding skills.

Now I have an /analyst, /engineer, and /devops that I talk to all day with their own logic and limitations, as well as the more general project CLAUDE.md, and dozens of docs/* files we collaborate on.

I'm at the point I'm running happy.engineering on my phone and don't even need to sit in front of the computer anymore.

darkwater 1/28/2026|||
Interesting!

I wonder if this line

> It will configure an auth_backend.rs and wire up a basic user

over a big enough number of projects will lead to at least 2-3 different user names.

UnlockedSecrets 1/28/2026|||
How much did this type of project cost you to make?
bojo 1/28/2026||
What kind of costs are you thinking?
UnlockedSecrets 1/28/2026||
money
nsainsbury 1/27/2026||
Touching on the atrophy point, I actually wrote a few thoughts about this yesterday: https://www.neilwithdata.com/outsourced-thinking

I actually disagree with Andrej here re: "Generation (writing code) and discrimination (reading code) are different capabilities in the brain." and I would argue that the only reason he can read code fluently, find issues, etc. is because he has spent year in a non-AI assisted world writing code. As time goes on, he will become substantially worse.

This also bodes incredibly poorly for the next generation, who will mostly in their formative years now avoid writing code and thus fail to even develop a idea of what good code is, how it works/why it works, why you make certain decisions, and not others, etc. and ultimately you will see them become utterly dependent on AI, unable to make progress without it.

IMO outsourcing thinking is going to have incredibly negative consequences for the world at large.

gwd 1/27/2026||
Is coding like piloting, where pilots need a certain number of hours of "flight time" to gain skills, and then a certain number of additional hours each year to maintain their skills? Do developers need to schedule in a certain number of "manually written lines of code" every year?
thoughtpeddler 1/27/2026|||
Read your blog post and agree with some of it. Largely I agree with the premise that the 2nd and 3rd order effects of this technology will be more impactful than the 1st order “I was able to code this app I wouldn’t have otherwise even attempted to”. But they are so hard to predict!
olafalo 1/28/2026|||
Thanks, this rings true to me. The struggle is an investment, and it pays off in good judgement and taste. The same goes for individual codebases too. When I see some weird bug and can immediately guess what’s going wrong and why, that’s my time spent in that codebase paying off. I guess LLM-ing a feature is the inverse, incurring some kind of cognitive debt.
nicodjimenez 1/28/2026||
great article and many great points here
bartoszcki 1/28/2026||
Feels like a combination of writing very detailed task descriptions and reviewing junior devs. It's horrible. I very much hope this won't be my job.
Geee 1/29/2026||
You let AI write your task descriptions. Try plan mode on CC.
woah 1/28/2026||
Probably won't be if you don't get good at it.
vibeprofessor 1/27/2026||
The AGI vibes with Claude Code are real, but the micromanagement tax is heavy. I spend most of my time babysitting agents.

I expect interviews will evolve into "build project X with an LLM while we watch" and audit of agent specs

maxdo 1/27/2026||
I've been doing vibe code interviews for nearly a year now. Most people are surprisingly bad with AI tools. We specifically ask them to bring their preferred tool, yet 20–30% still just copy-paste code from ChatGPT.

fun stats: corelation is real, people who were good at vibe code, also had offer(s) with other companies that didn't run vibe code interviews.

bflesch 1/27/2026|||
Interesting you say that, feels like when people were too stupid to google things and "googling something" was a skill that some had and others didn't.
xyzsparetimexyz 1/27/2026|||
Copy pasting from chatgpt is the most secure option.
maxdo 1/28/2026|||
Not going from home is the most secure way of going out.

It doesn’t work you can’t be productive without agent capable of doing queries to db etc

xyzsparetimexyz 1/28/2026||
>Not going from home is the most secure way of going out.

What? I can't parse this sentence. Maybe get an ai to rewrite it?

jatari 1/28/2026|||
Also the method that will result in the higher quality codebase.
0xy 1/27/2026|||
Sounds great to me. Leetcode is outdated and heavily abused by people who share the questions ahead of time in various forums and chats.
thefourthchime 1/27/2026||
From what I've heard, what few interviews there are for software engineers these days, they do have you use models and see how quickly you can build things.
iwontberude 1/27/2026||
The interviews I’ve given have asked about how control for AI slop without hurting your colleagues feelings. Anyone can prompt and build, the harder part, as usual for business, is knowing how and when to say, ‘no.’
nsb1 1/27/2026||
The best thing I ever told Claude to do was "Swear profusely when discussing code and code changes". Probably says more about me than Claude, but it makes me snicker.
fishtoaster 1/27/2026||
> if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side.

This is about where I'm at. I love pure claude code for code I don't care about, but for anything I'm working on with other people I need to audit the results - which I much prefer to do in an IDE.

wellpast 1/28/2026||
I coded up a crossword puzzle game using agentic dev this weekend. Claude and Codex/GPT. Had to seriously babysit and rewrite much of it, though, sure, I found it “cool” what it could do.

Writing code in many cases is faster to me than writing English (that is how PLs are designed, btw!) LLM/agentic is very “neat” but still a toy to the professional, I would say. I doubt reports like this one. For those of us building real world products with shelf-lives (Is Andrej representative of this archetype?), I just don’t see the value-add touted out there. I’d love to be proven wrong. But writing code (in code, not English), to me and many others, is still faster than reading/proving it.

I think there’s a combination of fetishizing and Stockholm syndroming going on in these enthusiastic self-reports. PMW.

jofla_net 1/28/2026|
>Writing code in many cases is faster to me than writing English

True, I feel as though i'd have to become Stienbeck to get it to do what i "really" wanted, with all the true nuance.

tomlockwood 1/28/2026|
Oh wow! Guy who's current project depends on AI being good is talking about AI being good.

Interesting.

More comments...