I’m one of those people.<p>Used Claude Code until September then Codex exclusively.<p>All my code has been AI generated, nothing by hand.<p>I review the code and if I don’t like something- I let it know how it should be changed.<p>Used to be a lot of back and forth in August, but these days GPT 5.2 Codex one shots everything so far. It worked for 40 hours for me one time to get a big thing in place and I’m happy with the code.<p>For bigger things start with a plan and go back and forth on different pieces, have it write it to an md file as you talk it through, feed it anything you can - user stories, test cases, design, whiteboards, backs of napkins and in the end it just writes the code for you.<p>Works great, can’t fathom going back to writing everything by hand.
Cool, the person who financially benefits from hyping AI is hyping AI.<p>What's with the ad here though?
The tweet from Dec 24 was interesting, why is Boris only <i>now</i> deciding to engage?<p>I refuse to believe real AI conversations of any value are happening on X.<p><i>Hi I'm Boris and I work on Claude Code. I am going to start being more active here on X, since there are a lot of AI and coding related convos happening here.</i><p><a href="https://xcancel.com/bcherny/status/2003916001851686951" rel="nofollow">https://xcancel.com/bcherny/status/2003916001851686951</a>
I wonder how.
Everything I let claude code majorly write, whether Go, F#, C or Python, I end up eventually at a point where I systematically rip it apart and start writing it over.<p>In my study days, we talked of “spikes”. Software or components which functionally addressed some need, but often was badly written and architected.<p>That’s what I think most resembles claude code output.<p>And I ask the llm to write todo-lists, break tasks into phases, maintain both larger docs on individual features and a highly condensed overview doc.
I also have written claude code like tools myself, run local LLMs and so on.
That is to say, I may still be “doing it wrong”, but I’m not entirely clueless .<p>The only place where claude code has nearly done the whole thing and largely left me with workable code was some react front-end work I did (and no, it wasn’t great either, just fair enough).
> I landed 259 PRs -- 497 commits, 40k lines added, 38k lines removed<p>I wonder how much of these 40k lines added/38k lines removed were just replacing the complete code of a previous PR created by Claude Code.<p>I'm happy that it's working for them (whatever that means), but shouldn't we see an exponential improvement in Claude Code in this case?
Claude Code user¹ says Claude Code wrote continuously incorrect code for the last hour.<p>I asked it to write Python code to retrieve a list of Kanbord boards using the official API. I gave it a link to the API docs. First, it wrote a wrong JSONRPC call. Then it invented a Python API call that does not exist. In a new try, I I mentioned that there is an official Python package that it could use (which is prominently described in the API docs). Claude proceeded to search the web and then used the wrong API call. Only after prompting it again, it used the correct API call - but still used an inelegant approach.<p>I still find some value in using Claude Code but I'm much happier writing code myself and rather teach kids and colleagues how to do stuff correctly than a machine.<p>¹) me
I’m nearly the same. Though I do find I’m still writing code, just not the code that’s ending up in the commit. I’ll write pseudo code, example code, rough function signatures then Claude writes the rest.
It shows, I have to kill it forcefully over 10 times per day.
View the full thread without Twitter/X account:
<a href="https://xcancel.com/bcherny/status/2004897269674639461" rel="nofollow">https://xcancel.com/bcherny/status/2004897269674639461</a>
"If the AI builds the house, the human must become the Architect who understands why the house exists."<p>In Japanese traditional carpentry (Miya-daiku), the master doesn't just cut wood. He reads the "heart of the tree" and decides the orientation based on the environment.<p>The author just proved that "cutting wood" (coding) is now automated. This is not the end of engineers, but the beginning of the "Age of Architects."<p>We must stop competing on syntax speed and start competing on Vision and Context.
honestly i've been becoming too lazy, I know exactly what I want and AI is at a point where it can turn that into code. It's good enough to a point where I start to design code around AI where it's easier for AI to understand (less DRY, less abtractions, closer to C)<p>And it's probably a bad thing? Not sure yet.
I just let myself use AI on non-critical software. Personal projects and projects without deadline or high quality standards.<p>If it uses anything I don't know, some tech I hadn't grasped yet, I do a markdown conversation summary and make sure to include technical solutions overview. I then shove that into note software for later and, at a convenient time, use that in study mode to make sure I understand implications of whatever AI chose. I'm mostly a backend developer and this has been a great html+css primer for me.
It is not bad. It is mastery.<p>You are treating the AI not as a tool, but as a "Material" (like wood or stone).<p>A master carpenter works <i>with</i> the grain of the wood, not against it. You are adapting your architectural style to the grain of the AI model to get the best result.<p>That is exactly what an Architect should do. Don't force the old rules (DRY) on a new material.
First I thought CC wrote all its code, but it’s about the engineer’s contributions to CC, which is quite different.
I'm sure it's unrelated(right guys? right?) but they had to revert a big update to CC this month.<p><a href="https://x.com/trq212/status/2001848726395269619" rel="nofollow">https://x.com/trq212/status/2001848726395269619</a>
What %age of his reversions this month are done by Claude? ;)
Not sure why you are getting downvoted, but this <i>IS</i> the key worry: That people lose contact with the code and really don’t understand what is going on, increasing “errors” in production (for some definition of error), that result in much more production firefighting that, then, reduce the amount of time to write code.
Losing contact with the code is definitely on my mind too. Just like how writing can be a method of thinking, so can programming. I fear that only by suffering through the implementation will you realise the flaws of your solution. If this is done by an LLM you are robbed the opportunity and produce a worse solution.<p>Still, I use LLM assisted coding fairly frequently, but this is a nagging feeling I have.
> Not sure why you are getting downvoted<p>A: The comment is bad for business.
I mean, that’s possible, but the more interesting datapoint would be “and then how much did you have to delete and/or redo because it was slop”
IMHO it's very misleading to claim that some LLM wrote all the code, if it's just a compression of thousands of peoples' codes that lead to this very LLM even having something to output.