Once you are popular, whatever said is automatically true
The Making of Claude Code
21–30 of 35 posts
Re: The Making of Claude Code
#22Aider was also some of the most amazing prior art.
After switching from the early copilot (crazy to think they were first to market with this stuff?) it was an amazing TUI experience.
CC won because it offered token hungry devs a fixed price for almost infinite usage in the early days with stacks of VC cash to burn.
Re: The Making of Claude Code
#23“The autonomous software engineering agent vision is more or less coming to fruition.”
Oddly enough no evidence of this is provided. I’ll admit it’s possible to have Claude write 100% of your code - however this is very distinct from autonomy. If I iterate on the code with Claude - telling it what to change, checking for errors and reporting them back to Claude, etc., I can build an app without “writing code” - but that is totally different from autonomy. And it’s not even clear how much of a time saver this really is if I know the language myself.
Re: The Making of Claude Code
#24Pi was written by like one guy and it's better than this
To be fair, Pi only had to be useful. Claude Code had to solve the difficult unsolved problem of making a terminal print text, so naturally they built a small game engine [1]
Re: The Making of Claude Code
#25Pi was written by like one guy and it's better than this
Can you be more specific about how one is better than the other?
Re: The Making of Claude Code
#26Pi was written by like one guy and it's better than this
Can you be more specific about how one is better than the other?
My own experience: much less context bloat, and hidden system prompts. Can tune it to your own workflow, instead of dealing with whatever hidden system prompt Claude Code forces on you.
Re: The Making of Claude Code
#27Perhaps the most telling part of this transcript is Tristan Hume, a prolific and talented programmer, and presumably an expert performance engineer, is repeatedly saying "this thing just doesn't work that well yet" or "it's just not there yet" and everyone else is kind of just fawning over it.
"It actually made something that worked. But when I tried using it, I found I didn’t like it. I need to wait for a Claude that has the taste ..."
Yes, I am familiar with that experience.
Re: The Making of Claude Code
#28Pi was written by like one guy and it's better than this
To be fair, Pi only had to be useful. Claude Code had to solve the difficult unsolved problem of making a terminal print text, so naturally they built a small game engine [1] [1] https://x.com/trq212/status/2014051501786931427
Hall of fame tweet. Can't believe it hasn't even been 6 months
Re: The Making of Claude Code
#29Earlier quoted context omitted.
Can you be more specific about how one is better than the other?
My own experience: much less context bloat, and hidden system prompts. Can tune it to your own workflow, instead of dealing with whatever hidden system prompt Claude Code forces on you.
Thanks! What about OpenCode? I'm trying it out right now and would love to learn your thoughts or feedback.
Re: The Making of Claude Code
#30Incredibly cringe. Literally every single medium mode problem for a team is framed as a groundbreaking achievement. These people snort their own farts.
Yeah for sure lmao.
> @dawn-drain — Research Engineer at Anthropic My main project for my first three years at Anthropic, beginning in 2021, was to try and make a model that was as good at coding as possible— at least as good as me.