As I understand it, it was originally meant for “throwaway weekend projects”, but then the MBAs got a hold of the term and if you look at job postings nowadays, some companies are really pushing for “AI-first” workers.
The desire obviously isn’t just to increase existing dev velocity, but the devalue skills and experience that come from formal education and years of practical learning. Basically to reduce the bargaining power / cost of programmers.
This guy gives a very good rundown on what vibe coding is and how to use it. Basically it’s generating code with AI and then going over it like a copy editor. The important point he makes is that the dev should understand and vet everything the code is doing, not expect to type in “Write an inventory tracking system” and be done. It reminds me of people’s misconceptions about Object Oriented Programming in the early 90s. Some thought it meant you just create an object called Payroll with a method doPayroll() and some magic happened.
As I understand it, it was originally meant for “throwaway weekend projects”, but then the MBAs got a hold of the term and if you look at job postings nowadays, some companies are really pushing for “AI-first” workers.
The desire obviously isn’t just to increase existing dev velocity, but the devalue skills and experience that come from formal education and years of practical learning. Basically to reduce the bargaining power / cost of programmers.
This guy gives a very good rundown on what vibe coding is and how to use it. Basically it’s generating code with AI and then going over it like a copy editor. The important point he makes is that the dev should understand and vet everything the code is doing, not expect to type in “Write an inventory tracking system” and be done. It reminds me of people’s misconceptions about Object Oriented Programming in the early 90s. Some thought it meant you just create an object called Payroll with a method doPayroll() and some magic happened.