Vibe coding is interacting with the codebase via prompts. As the implementation is hidden from the “vibe coder”, all the engineering concerns will inevitably get ignored. Many of the concerns are hard to express in a prompt, and many of them are hard to verify by only inspecting the final artifact. Historically, all engineering practices have tried to shift all those concerns left – to the earlier stages of development when they’re cheap to address. Yet with vibe coding, they’re shifted very far to the right – when addressing them is expensive.
The question of whether an AI system can perform the complete engineering cycle and build and evolve software the same way a human can remains open. However, there are no signs of it being able to do so at this point, and if it one day happens, it won’t have anything to do with vibe coding – at least the way it’s defined today.
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community’s icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
- 0 users online
- 36 users / day
- 255 users / week
- 646 users / month
- 1.28K users / 6 months
- 1 subscriber
- 1.67K Posts
- 28.2K Comments
- Modlog
I’m already sick of this phrase. The tech hallucinates too much, and understands security about as much as a whale understands astrophysics.
Everything an LLM outputs is a hallucination, and sometimes that hallucination lines up with reality.
That feeling when LLM matches your worldview.
Also, this. (Not LLM, but still beautifully disturbing.)
As a leftist, I oppose far-right development.