171–180 of 221 posts
> What I needed was not a better app, but a way to tolerate imperfection without the whole system falling apart. > Claude did not invent that idea. It executed it. > Claude handled implementation. I handled taste. This style of writing always gets me now :)
Earlier quoted context omitted.
It seems like it's approaching a horizontal asymptote to me, or is at the very least concave down. You might be describing a state 50 years from now.
It seems like progress is accelerating, not slowing down. ARC AGI 2: https://x.com/poetiq_ai/status/2003546910427361402 METR: https://metr.org/blog/2025-03-19-measuring-ai-ability-to-com...
The knowledge necessary to do real work with these things is still mostly locked up in the humans that have traditionally done that work.
Earlier quoted context omitted.
Opus 4.5 is just a few days over a month old. Boris would have had access to that for a while before its release though.
Boris is someone that is employed by Anthropic and has a massive stake in them going public, standing to make millions. They are by definition a biased source and should not be referenced as such.
I do however think he is not an actively dishonest source. When he says "In the last thirty days, I landed 259 PRs -- 497 commits, 40k lines added, 38k lines removed. Every single line was written by Claude Code + Opus 4.5." I believe he is telling the truth.
That's what dogfooding your own product looks like!
> What I needed was not a better app, but a way to tolerate imperfection without the whole system falling apart. > Claude did not invent that idea. It executed it. > Claude handled implementation. I handled taste. This style of writing always gets me now :)
Others, please chime in, I want to take a sort of poll here: I usually grimace at "GPT smell". The lines you quoted stood out to me as well, but I interpreted them as "early career blogger smell". It's similar, but it didn't come off as AI. I think because it avoided grandiose words, and because it reused the exact same phrase format (like a human tic) rather than randomly sampling the format category (like an AI). T…
Many weaker or non-native writers might use AI for that "editor's eye" without realizing that they are being driven to sound identical to every other blog post these days. And while I'm certainly growing tired of constantly reading the same LLM style, it's hard to fault someone for wanting to polish what they publish.
Earlier quoted context omitted.
Forget utterly groundbreaking things, I want to hear maintainers of complex, actively developed, and widely used open-source projects (e.g. ffmpeg, curl, openssh, sqlite) start touting a massive uptick in positive contributions, pointing to a concrete influx of high-quality AI-assisted commits. If AI is indeed a 10x force multiplier, shouldn't these projects have seen 10 years' worth of development in the last year?…
> I want to hear maintainers of complex, actively developed, and widely used open-source projects (e.g. ffmpeg, curl, openssh, sqlite) start touting a massive uptick in positive contributions That's obviously not going to happen, because AI tools can't solve for taste. Just because a developer can churn out working code with an LLM doesn't mean they have the skills to figure out what the right working code to contrib…
> I own more books than I can read. > I started asking for things I did not need. For a community that prides itself on depth of conversation, ideas, etc. I'm surprised to so much praise for a post like this. I'll be the skeptic. What does it bring to you to vibe code your vibe shelf? To me, this project perfectly encapsulates the uselessness of AI, small projects like this are good learning or relearning experience…
I've actually been working on something similar since I also had this pain (plus I'm too cheap to buy all the books I'm reading)
To solve the issue related to having take the photos myself, I scrape from places like eBay to get the accurate spine images. Obviously this isn't 100% accurate, but like you I also decided 90% accuracy is good enough.
I am yet to see a vibe coded success that isn't a small program that already exists in multiple forms in the training data. Let's see something ground-breaking. If AI coding is so great and is going to take us to 10x or 100x productivity let's see it generate a new, highly efficient compression algorithm or a state-of-art travelling salesman solution.
90-99% of an engineer's work isn't entirely novel coding that has never existed before, so by succeeding at what "already exists", it can take us to 10x-100x productivity.
The automation of all that work is groundbreaking in and of itself.
I think that, for a while into the future at least, humans will be relegated to generating that groundbreaking work, and the AI will increasingly handle the rest.
Earlier quoted context omitted.
> I want to hear maintainers of complex, actively developed, and widely used open-source projects (e.g. ffmpeg, curl, openssh, sqlite) start touting a massive uptick in positive contributions That's obviously not going to happen, because AI tools can't solve for taste. Just because a developer can churn out working code with an LLM doesn't mean they have the skills to figure out what the right working code to contrib…
No, Simon, we don't "refuse". We are just very selective and there is a lot of paperwork involved to confirm the contribution is in the public domain and does not contaminate the SQLite core with licensed code. Please put the false narrative that "SQLite refuses outside contributions" to rest. The bar is high to get there, but the SQLite code base does contain contributed code.
Found that paperwork here: https://www.sqlite.org/copyright-release.html
I will make sure not to spread that misinformation further in the future!
Update: I had a look in fossil and counted 38 contributors:
brew install fossil
fossil clone https://www.sqlite.org/src sqlite.fossil
fossil sql -R sqlite.fossil "
SELECT user, COUNT(*) as commits
FROM event WHERE type='ci'
GROUP BY user ORDER BY commits DESC
"
These are the perfect size projects vibe coding is currently good for. At some point you hit a project size that is too large or has too many interdependencies, and you have to be very careful about how you manage the context and should expect the llm to start generating too much code or subtle bugs. Once you hit that size, in my opinion, it's usually best to drop back to brainstorming mode, only use the llm to help…
I agree with you as far as project size for vibe-coding goes - as-in often not even looking at the generated code. But I have no issues with using Claude Code to write code in larger projects, including adapting to existing patterns, it’s just not vibe coding - I architect the modules, and I know more or less exactly what I want the end result to be. I review all code in detail to make sure it’s precisely what I want…