Video / Short
Vibe Coding Is Changing What "Developer" Means
Pete Cooper explains where vibe coding fits in a Scrum or Agile development cycle and where it stops being enough. He argues that quick demos still need a planning step before they can become a product.
Video summary
Pete Cooper looks at how vibe coding has affected the software development life cycle at the operational level, when you are actually running a project. He describes vibe coding as using an LLM to create a demo without needing much coding skill.
He says his team, like many others, runs development with Scrum or Agile, in fast iterations of usually one or two weeks where you build something and get feedback quickly. Vibe coding fits that well, in his view, because it lets you demo things quickly.
The catch is that you still need to spend time specifying what you are doing. He calls this a spike, building an understanding of how you will build something before you build it. That step, he says, is what lets the work fit into the architecture and become a real product when the time comes.
Video transcript
Read the spoken content without loading the YouTube player.
So, how has Vibe coding affected software development life cycle at the grassroots level, at the operational level, when you actually running project? Now, Vibe coding is where you use an LLM to create a demo, and you don't need a lot of coding skills. And the software development cycle, the way we run it and a lot of other people do, is using Scrum or Agile. And these are fast iterations, usually 1 or 2 weeks, where you build stuff and you get feedback quickly. Does Vibe Vibe coding fit into that? Well, yes, it does, cuz it enables you to quickly demo stuff.
But, the key thing that you need to keep your eye on, if you're doing software development, is you still need to spend time specifying what is you're doing. We call it a spike. Spiking, or developing a understanding of how you're going to build it before you build it, is still an important piece if you're going to build a product, because that allows you to put it into the architecture, make sure that you can actually turn this into a product when that time comes.