When you vibe code, you are incurring tech debt as fast as the LLM can spit it out. Which is why vibe coding is perfect for prototypes and throwaway projects: It’s only legacy code if you have to maintain it!
The worst possible situation is to have a non-programmer vibe code a large project that they intend to maintain. This would be the equivalent of giving a credit card to a child without first explaining the concept of debt.
If you don’t understand the code, your only recourse is to ask AI to fix it for you, which is like paying off credit card debt with another credit card.
A thoughtful approach from Sam:
- Use AI only for tasks you already know how to do, on occasions when the time that would be spent completing the task can be better spent on other problems.
- When using AI, provide the chosen tool with something you’ve made as an input along with a specific prompt.
- Always comprehensively review the output from an AI tool for quality.
- I don’t and won’t use “AI” in the text of any of my published work.
- I’m not worried about “AI” replacing me as a novelist.
- People in general are burning out on “AI.”
- I’m supporting human artists, including as they relate to my own work.
- “AI” is Probably Sticking Around In Some Form.
- “AI” is a marketing term, not a technical one, and encompasses different technologies.
- There were and are ethical ways to have trained generative “AI” but because they weren’t done, the entire field is suspect.
- The various processes lumped into “AI” are likely to be integrated into programs and applications that are in business and creative workflows.
- It’s all right to be informed about the state of the art when it comes to “AI.”
- Some people are being made to use “AI” as a condition of their jobs. Maybe don’t give them too much shit for it.
We’ve been taught that technological change must be chaotic, uncontrolled, and socially destructive — that anything less isn’t real innovation.
The conflation of progress with disruption serves specific interests. It benefits those who profit from rapid, uncontrolled deployment. “You can’t stop progress” is a very convenient argument when you’re the one profiting from the chaos, when your business model depends on moving fast and breaking things before anyone can evaluate whether those things should be broken.
We’ve internalized technological determinism so completely that choosing not to adopt something — or choosing to adopt it slowly, carefully, with conditions — feels like naive resistance to inevitable progress. But “inevitable” is doing a lot of work in that sentence. Inevitable for whom? Inevitable according to whom?
I love the small web, the clean web. I hate tech bloat.
And LLMs are the ultimate bloat.
So much truth in one story:
They built a machine to gentrify the English language.
They have built a machine that weaponizes mediocrity and sells it as perfection.
They are strip-mining your confidence to sell you back a synthetic version of it.
I suppose it’s not clear to me what a ‘good’ window into unreliable, systemically toxic systems accomplishes, or how it changes anything that matters for the better, or what that idea even means at all. I don’t understand how “ethical AI” isn’t just “clean coal” or “natural gas.” The power of normalization as four generations are raised breathing low doses of aerosolized neurotoxins; the alternative was called “unleaded”, but the poison was called “regular gas”.
There’s a real technology here, somewhere. Stochastic pattern recognition seems like a powerful tool for solving some problems. But solving a problem starts at the problem, not working backwards from the tools.
Brian Eno on prototyping and fidelity.
Wake me up when we get to the plateau of productivity.
Language matters.
A large language model is as neutral as an AK-47.
The best of the web is under continuous attack from the technology that powers your generative “AI” tools.