When you first start you have like 20 files. But what happens when you have sixty, seventy edge functions? Lovable is gonna read all of those, and it's gonna consume 80% of the token allocation on reading, leaving only 20% for thinking and executing.
“And then your code base gets bigger and bigger and bigger and bigger and bigger.”
And then your code base gets bigger and bigger and bigger and bigger and bigger. Like when you when you first start you have like 20 files. It's it can read 20 files. But what what happens when you have I'm just building a project right now that has, like, sixty, seventy edge function functions. Right? What happens then when I say this broke and there's no reference which edge function does what? Guess what? Level is gonna read all of those, and it's gonna consume 80% of the token allocation on reading to get clarity, leaving only the final 20% for thinking and executing.
Why this clip
Technical insight about AI coding limitations with specific numbers and clear cause-effect relationship. Shows scaling challenges in AI development with concrete percentages that make the problem tangible.
More from this episode
From the blog
Want clips like this for your podcast?
We find your top 5-8 clips, write the hooks, and deliver ready-to-post content. First 2 episodes are free.
Get 2 Episodes Clipped Free