Last Friday at “This Week in Testing”, we touched on the topic of the “vibe coding” movement.
I assume that vibe coding will grow up and people will use it for real engineering, with the “turn your brain off” version of it sticking around just for prototyping and fun projects. For me, vibe coding just means letting the AI do the work. How closely you choose to pay attention to the AI’s work depends solely on the problem at hand. For production, you pay attention; for prototypes, you chill. Either way, it’s vibe coding if you didn’t write it by hand. (c) Steve Yegge
As a start, read:
- Revenge of the junior developer
- Here’s how I use LLMs to help me write code
- Hallucinations in code are the least dangerous form of LLM mistakes
Fun video: Interview with Vibe Coder in 2025
What do you think? Is it the future of delivering software or a trend that will last for a year?
How will vibe coding impact the testing? Will it generate more bugs? Will the systems become less reliable?
How can vibe coding/testing impact those who are just starting their careers?