5 ms·
1/4 of startups in YC current cohort have almost entirely AI-generated codebases
- OriginalMrPink 2y agoIt would have been great if they had disclosed which products. I've been building tons of projects with AI lately, and while this is a massive productivity boost, the code itself doesn't scale. The acceleration when you start with zero is massive, but with a growing code base, AI hits a wall at some point. You better understand what you've built going from there.
- xhkkffbf 2y agoI watched this happen decades ago. Smart coders knew about memory allocations. Okay coders just assumed that the garbage collector would handle it. One friend of mine wrote code that was 1000 times faster than the people in the next cubicle over. Why? Because he was careful with memory usage and didn't trigger the virtual memory thrashing. AI is just another form of automation.
- zero_shift 2y agoThere must be a name for the self-balancing phenomenon where any improvement in productivity is soon swallowed up by an equal increase in waste
- jxjnskkzxxhx 2y agoMust be it be swallowed up? Is it not possible that an improvement in productivity increases but still be net positive? I believe that's what happens in the real world.
- UncleEntity 2y ago> Must be it be swallowed up? Yes. Because user CPU cycles are cheaper than developer brain power.
- tjalfi 2y agoAre you referring to Jevon's Paradox[0]? [0] https://en.wikipedia.org/wiki/Jevons_paradox https://en.wikipedia.org/wiki/Jevons_paradox
- zero_shift 2y agoI guess it's a variant of that, Jevon's Paradox being that increasing supply counterintuitively increases demand
- cpeterso 2y agoNathan Myhrvold said “Software is a gas; it expands to fill its container.”
- Karellen 2y agoYeah, these new-fangled "compilers" will never catch on. Programmers who rely on them will stop learning machine code, and won't know how their program really works. That's if the compiler actually compiles your code at all, without throwing an internal error, making you change your (correct) code around arbitrarily until it actually accepts it. But at least with an internal compiler error you know the compiler has broken - rather than it silently miscompiling your code to do the wrong thing. But even then, even if the compiler accepts your code without barfing, and generates correct machine code from it, it still won't generate as efficient machine code as you could write by hand yourself. Nope, these compilers will never catch on, and never get reliable enough to be useful for serious software engineering. -- Some programmer circa 1975, probably, who lives in my head mumbling this to themselves whenever I'm sure generative-AI-based "programming" is a crock of shit. Although, to be fair, the 2005-era developer who is drunkenly ranting that UML diagrams will make programming 100x more productive any day now, is a handy counterpoint.
- SR2Z 2y agoI mean, the difference between a computer and an LLM is correctness. The compiler MUST conform exactly to a spec. An LLM is useful precisely because it does not.
- deleted 2y ago[deleted]
- feoren 2y ago> One friend of mine wrote code that was 1000 times faster than the people in the next cubicle over And did that 1000x speedup make a difference to users? Are we talking about an on-click event that now took 10μs instead of 10ms? Was this a 1000x speedup in a hot critical-path bottleneck, or was it an already quick in-memory post-processing operation that fired after waiting 30 seconds on a sluggish database query? Sorry to doubt so much, but the vast majority of times someone boasts about a speedup like this, it turns out to be done for bragging rights rather than for the benefit of the project. A 1000x speedup is only impressive if you can show that the time you improved upon was actually a problem.
- bluefirebrand 2y ago> while this is a massive productivity boost, the code itself doesn't scale Then it's not a productivity boost imo "Produces more tech debt faster" is the worst possible outcome of a 'productivity' tool
- scarface_74 2y agoI think you misunderstand the purpose. Who cares if it adds technical debt later if your goal is just to have something to show off to get investments? The goal of every startup is to get funding and an exit. The concern is not long term maintainability.
- bluefirebrand 2y ago> Who cares if it adds technical debt later if your goal is just to have something to show off to get investments? The goal of every startup is to get funding and an exit. The concern is not long term maintainability Not everyone works in startups, specifically to avoid this disgusting mentality If I had to deal with this "build garbage quickly to get money and run before the house of cards collapses" mentality in my day to day life I would put my face into a wood chipper I loathe people who think this way, and it is so miserable that all tech is becoming just a vehicle for this sort of grift Robbing banks at gunpoint is more honest
- JustExAWS 2y agoThe article is specifically about YC companies - by definition early stage startups.
- WJW 2y agoEven for the small subset of companies for which this is true, you need to have a successful exit at all. Technical debt is fine from that perspective, but only if the whole thing comes crashing down AFTER you sell. If it comes crashing down too soon, you have done nothing but waste a few years of your life. Remember that most successful exits happen more than 5 years after founding. Having an AI vomit out a prototype in a week vs doing it yourself in 4 might get you seed funding marginally faster, but if it delays product development more than 3 weeks over the next 4-5 years it's still not worth it.
- ph4evers 2y agoI'm not surprised. There is a complete meltdown in the Cursor subreddit because some update made code generation worse in "agent" mode. It seems that there are many people completely relying on prompting without reviewing any code at all.
- bluefirebrand 2y agoCode Review is vital, but probably the least enjoyed part of any software job I cannot fathom why anyone who writes and maintain code would embrace AI tools that essentially shift their job to be more code review and less coding Especially given the quality of AI generated code is all over the place People say "it's like a good junior" but I disagree wholeheartedly. Good juniors eventually stop making the same mistakes
- yimby2001 2y agoI mean it has improved greatly about as fast as an actual junior programmer…
- bluefirebrand 2y agoAny given model never improves ever The overall technology may. A new model may be better than an old model But a model is fixed That's the difference
- yCombLinks 2y agoWorthless argument, no one cares if chatGPT 3 was a good code in their day job.
- bluefirebrand 2y agoThis is relevant when companies are paying for access to specific models and are restricting their employees access to other models Your model isn't improving Get ready to jump on the "pay us more for better models" treadmill or get left behind
- Karellen 2y ago> During the discussion, Hu said that even if product builders rely heavily on AI, one skill they would have to be good at is reading the code and finding bugs. Naturally, that brings to mind the classic: > Everyone knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it? -- Brian Kernighan, The Elements of Programming Style And also: > Programs must be written for people to read, and only incidentally for machines to execute. -- Abelson & Sussman, Structure and Interpretation of Computer Programs
- Prosammer 2y ago>So if you're as clever as you can be when you wrote it, how will you ever debug it? LLMs do not write very "clever" code by default. Without prompting them continuously to make it more "clever", they tend to write lots and lots of simple code, vs writing "clever" code that reduces redundant code, improves performance, etc. What I am curious about is if these slop-filled codebases will be a problem or not in the future - traditionally it's been bad practice to have duplicate code everywhere, but with LLMs it feels like it matters less, as long as the code is simple and readable.
- evil-olive 2y ago> traditionally it's been bad practice to have duplicate code everywhere, but with LLMs it feels like it matters less, as long as the code is simple and readable. duplicate code is a bad practice "traditionally" because it means if you have a bug, you have to fix it in N spots (each of which may have drifted to be slightly different) instead of just 1. how do LLMs improve that? if you have a bug (which everyone seems to agree happens more often with LLM-generated code) you'll still need to fix it in N spots. being able to feed those N instances into the LLM and ask it to fix the bug maybe speeds the process up a little, but it doesn't solve the underlying problem. when I got into the industry in the 2000s, saving costs by outsourcing to India was the hype cycle of the day. would you have the same opinion that duplicate code doesn't matter, because you can just pay cheap outsourced engineers to make those N redundant bugfixes?
- danjl 2y agoThis says a lot more about YC than it does about AI based programming.
- dkkergoog 2y ago[dead]
- conartist6 2y ago"This isn’t a fad. This isn’t going away. This is the dominant way to code. And if you are not doing it, you might just be left behind" To which I say: a race to the bottom is still a race, yes, but not one you want to win
- Evil_Saint 2y agoThis is exactly how I feel. It's like they are racing to find the shittiest viable product.
- janalsncm 2y agoWell AI is best at greenfield projects, so it makes sense. What would be interesting to track is the amount of code still written by AI after 1 year or more if the company still exists. I think our initial reactions as SWEs may be to dismiss this, but if non technical folks (who might be closer to a real customer need) can spin something up to get traction, that’s a win. What is important is delivering value to end users. I wonder how many genuinely good business ideas never happened in the past because a technical cofounder wasn’t available.
- evil-olive 2y ago> In a video titled “Vibe Coding Is the Future,” Friedman, along with YC CEO Garry Tan, managing partner Harj Taggar, and general partner Diana Hu, discussed the trend of using natural language and instincts to create code. how many YC-backed startups (in general, not just the current batch) have products based in some way on LLM code-generation? it seems like there's a significant chance for a conflict of interest here, where YC has an incentive to build up hype about LLM-generated codebases in order to benefit their overall portfolio. will we see a follow-up story several months or a year from now, comparing how these startups have fared relative to the other 3/4ths of the batch? if one of them is a success, probably. if all of them fizzle out...maybe not.
- _fat_santa 2y agoI recently started using cursor for my side business and it's been amazing so far. I found that it works best for simple questions where I would normally go to stack overflow and for "drudge work". One example of "drudge work" is that I'm currently refactoring all strings in the app. Before cursor, it would take me upwards of an hour to refactor the strings in a complex component but now I can just shove all that into cursor and have it do it for me. For simple questions it sometimes works great and other times just falls apart. In one scenario I asked it why my sequelize query didn't return the data I expected and it immediately gave me a fix. But in another scenario I asked it how to refactor out a "forwardRef" in a component and it just kept recommending that I leave the code as is.
- PeterStuer 2y agoI use AI every day while coding. I love it. And hey, I get both Techcrunch and YC need clickbaity, hyperbolic PR, but guys, don't jump the shark on this. 95%? I wish! Either they have access to some seriously next NeXt NEXT gen stuff, or this is pure nonsense, exaggerated by at least half an order of magnitude.
- torginus 2y agoI feel like this is not a very insightful take - you can have an AI generated codebase where every function is generated by prompting from humans - such a codebase could be pretty good indeed. However, in my experience using these reasoning models to generate giant chunks of code usually has disastrous results and barely even works even when working from a clean sheet.
- namshe 2y agoPrediction: soon we will see the first vibes based billionaire. They'll have no idea what they did, what their product does, how it works, or any possible ethical implications of having developed it. But they'll be fucking rich.
- Aaronrego120 2y agoAdam neuman says hi!
- namshe 2y agoFunny enough, I was consulting at WeWork the day he stepped down. Very interesting day. And agree, great case in point.