Earlier quoted context omitted.
The upper bound on program complexity used to be the power of the human mind. "Vibe coding" can break through that barrier. But not because the problem being solved needs that complexity. Because the process does not drive itself towards compact abstractions. It's the AI-powered version of the scaling problem Brooks described back in "The Mythical Man-Month". The combinatoric problems get worse with scale. Concretely…
The question is that if it can go beyond the upper limit of human mind complexity, would we be able to understand it or use it? I cannot remember who it was but there was an author who was traveling with their dog. They noticed that their dog would always pee on various tree to mark them as their territory. On their travels they ended up need some giant Red wood trees and figured, "I want to give my dog the ultimate…
The Tower Keeps Rising
171–180 of 280 posts
Re: The Tower Keeps Rising
#172Don't let the agent scratch that itch - it is your hungry inner programmer expressing the need to eat i.e. do it correctly as per your taste. That morsel of work is sustenance.
It also activates the thinking gears that only kick in when I am writing the code. In the same process, the code sinks in better and becomes part of the mental model, even if I may not have paid attention to every single line.
I have also noticed that the mode switch puts me in a marginally better mood - sort of a recharge for the next bout of prompt->change->prompt.
Re: The Tower Keeps Rising
#173> But it’s not the biblical story. At Babel, the loss of common language stops construction whereas in AI-assisted engineering, construction can continue after shared understanding has already collapsed. The lack of an immediate failure is what makes it curious and a bit disorienting. The tower does not fall, and so we do not notice what was lost. It just keeps rising. I don't know whether the author thinks this is a…
Re: The Tower Keeps Rising
#174> But it’s not the biblical story. At Babel, the loss of common language stops construction whereas in AI-assisted engineering, construction can continue after shared understanding has already collapsed. The lack of an immediate failure is what makes it curious and a bit disorienting. The tower does not fall, and so we do not notice what was lost. It just keeps rising. I don't know whether the author thinks this is a…
> Intelligence is knowing that a tomato is a fruit Intelligence is learning to avoid using childish cliches, unless your intention was to mislead. Categorisation and understanding dependencies are hard enough problems already. At the supermarket or taxation (Nix v. Hedden) tomatoes are a vegetable.
Re: The Tower Keeps Rising
#175I don't think we have hit a long enough timescale to say that we _can_ actually build on top of the AI-assisted engineering work. Tech debt tends to reveal itself later on in the process.
Personally I've totally witnessed AI-assisted work that is clearly heading towards a brick wall quite quickly. I think "mixed feelings" is my optimistic view.
People really discount how well _well engineered abstractions_ are required for AI tooling to not generate absolute garbage. And if people are relying on AI tooling for the abstractions... I think you're really tempting fate in the mid-term.
Re: The Tower Keeps Rising
#176Earlier quoted context omitted.
I'll meet you in the middle: an LLM "understands" words in the same way a toddler understands the phrases they say. How'd your toddler do at IMO last year?
Ask an LLM for the difference between a definite and indefinite article, and then pronouns. Maybe just a whole run down of basic grammar. And then read the comment again.
Re: The Tower Keeps Rising
#177Earlier quoted context omitted.
Ask an LLM for the difference between a definite and indefinite article, and then pronouns. Maybe just a whole run down of basic grammar. And then read the comment again.
Why don't you do that, since you're the one who has no idea what will happen?
Re: The Tower Keeps Rising
#178> But it’s not the biblical story. At Babel, the loss of common language stops construction whereas in AI-assisted engineering, construction can continue after shared understanding has already collapsed. The lack of an immediate failure is what makes it curious and a bit disorienting. The tower does not fall, and so we do not notice what was lost. It just keeps rising. I don't know whether the author thinks this is a…
What LLMs lack, from my experience, is two things: First, a long term memory (even a zoomed out one) and Second, the ability to execute a multi-step task without fizzling out. Upon adversity, LLMs breakdown and start making shit up. The newer models are better (and that's the difference between Fable/5.6 and GLM 5.2) but still have a very limited ability to execute any tedious planning tasks.
Re: The Tower Keeps Rising
#179Re: The Tower Keeps Rising
#180Earlier quoted context omitted.
Do you have specifics? It would be interesting to see what kind of improvements are possible.
I just see in my usage that I can release tens of features a day, whereas I'd be able to release one or two a day usually. I don't know if it's 100x, but it's definitely more than 10x. I've written up my process here: https://www.stavros.io/posts/how-i-write-software-with-llms/ The biggest thing to get right is to let the LLMs do what they're great at (code implementation from very detailed specs, and code review), a…