How can developers shift efficiently between Vibe Coding and Vibe Debugging without breaking their flow?
What are your go-to methods for staying in the groove while switching between these two modes? @TMosh @paulinpaloalto @dtonhofer
1 Like
I don’t use “vibe coding”, so I have no opinion on this.
3 Likes
But nowadays, vibe coding is being increasingly adopted in practice, reshaping traditional coding approaches. This shift is having a significant impact on the new generation of coders, influencing how they approach problem-solving and development.
That’s fine. I don’t have to use it if it doesn’t meet my needs.
1 Like
This vibe coding thing doesn’t make great sense to me, but I’m kinda old school
Is it like exploratory programming with background music?
I suspect I lost 10 years of my life uselessly debugging the stuff my cow-orkers vibed into life. No plan, no documentation and no design. But always fast in delivery. It wasn’t great.
Luckily we didn’t kill anyone.
1 Like
Well, Fireship has just come out with a top notch report 
1 Like
@dtonhofer Nice video. And I agree with No plan, no documentation and no design 