Yes, absolutely. In fact that's a big feature now in Autodesk. 99% of the design of a house is "detailing". Where does power line #8128 go? Does floor section 38 have the right slope? How big should water line #92 be and does it fit with sewage line #33 while it's sloping in the correct direction? We can't get electrical socket type 33, please modify everywhere in the design so we can use type 35 instead. And so on and so forth.
Human architects and engineers make TONS of mistakes in these designs all the time. Then builders and contractors fix them, or in many cases "fix" them, as I'm sure most people here have experienced.
Also if vibecoding houses can lead to a large increase in housing supply, as it should: Hurray!
> Also if vibecoding houses can lead to a large increase in housing supply, as it should: Hurray!
I love how well this captures the credibility of zealots and how some won't hesitate to exploit human suffering to push an agenda. The housing crisis is driven by regulation that lowers supply, shaped by greed and cruelty. Turning house designs into slop won't solve anything.
You want to see how AI actually contributes to the housing crisis? Then here's an actual example:
As a non-tech engineer (mechanical, trains) it's fascinating seeing what is essentially the "not real engineers" SWE crew finally pay the piper because they've invoked what is in essence a non-compliant, cost-focused subcontractor and now need all of the same engineering rigours they never previously understood.
Every large project in the coming back to waterfall. While the problems are certainly known and it was ultimately developed as a straw man, everything else ends up working worse. That said, you shouldn't be thinking pure waterfall as it's drawn up as a strawman, but rather a waterfall variation with feedback loops. But in the end, in very, very many cases, you have to know an end date in order to get things done because so many other things depend on you being done at the same time. If something is going to get done sooner you can't use it anyway without all the other pieces.
I won't call it "opinionated about how to use the language correctly."
Space is valid and it compile, Tab don't --- that's it.
When one say "opinionated about how to use the language correctly", I would think JavaScript with or without end of statement semicolon and being yell at even when your program works.
I mean, like any other skill that has pretty much been my experience (though I tried fusion + openscad), but there is something about being able to ask a computer all the dumb noob questions that makes that first phase easier.
It does, because it allows for quickly sharing a prepared response instead of saying the same thing over and over. It also works because the kind of person this link gets sent to is already used to trusting random websites over their human interactions.
And if we don't (like me), I think it can be assumed that we can find out.
A basic search tells me they're both ways to speed up applications/projects through memory management and storing of the memory/data in RAM. So the person in the article is asking a co-worker their opinion on which tool they should use for optimization/performance in their project, which is why an LLM response is less helpful than his co-worker's actual thoughts: comparisons of technical tools at a high or feature level are pretty easy to find and the decision of which to use often boils down to project specific variables, so what the author is asking of the co-worker relies on the co-worker's knowledge of their specific project.
I could also probably explain this just fine to non-tech people. It wouldn't be the most complete or technically accurate explanation, but it would be fine.
Most people write based on their experience and culture.
reply