Vibe coding vs Vibe engineering: 🅰️ Using AI to operate on the 𝘱𝘳𝘰𝘥𝘶𝘤𝘵 🆚 🅱️ Using AI to operate on the 𝘤𝘰𝘥𝘦 The former is vibing the later is engineering. Obviously you might be thinking: “the code is the means to operate on the product! These are the same!” I believe on a long enough lifetime, for the vast majority of software, they will be. Products like @v0 and @lovable_dev exist in the former category. At @vercel however our heart is in engineering the best possible products, with the highest possibly quality, which means also having clean ejection and interoperability points with formal engineering tools. I believe there’ll be ample success and large markets for both vibing and engineering. It’s very likely vibing will become more *opinionated* over time, to make the reliability, security and quality bar *everyone* wants. As an example, just yesterday I watched a demo of a highly opinionated full-vibing platform being built on Vercel that delivers better outcomes than engineers, due to the constraints and opinions it imposes. AI in the service of slop is a temporary, “AI interest rates phenomenon” (AIRP), a period in time where people paid for the fascination of using AI even though the outcome looks like deformed Will Smith in software form. Our focus at @vercel continues to be AI in the service of quality, not just productivity alone.