I don't know what you wrote in this book or why you decided to write it at all because I think "vibe coding" should die in oblivion and shame like Clippy, but from the start, vibe coding is one of the most abhorrent and delusional endeavours. I "vibe" coded a web page and after over 2 hours of fighting with the generated output I felt like throwing my monitor out of the window.
Love the angle on executable specifications over prompt colletions. The real friction in AI tooling is when teams confuse faster codegen with actually reducing technical debt. That provider-agnostic approch sounds way more durable than optimizing for whichever model du jour is trending.
I don't know what you wrote in this book or why you decided to write it at all because I think "vibe coding" should die in oblivion and shame like Clippy, but from the start, vibe coding is one of the most abhorrent and delusional endeavours. I "vibe" coded a web page and after over 2 hours of fighting with the generated output I felt like throwing my monitor out of the window.
And the name, Vibe engineering 🤦♂️ It is an oxymoron. I guess I can be a "vibe plumber" or a "vibe doctor" or a "vibe electrician".
Love the angle on executable specifications over prompt colletions. The real friction in AI tooling is when teams confuse faster codegen with actually reducing technical debt. That provider-agnostic approch sounds way more durable than optimizing for whichever model du jour is trending.