Why do we need a term for any of it, other than "coding". Before AI, I did not need different terms for coding when some devs would cowboy-code buggy slop straight to production vs. a full team doing test-driven development with dedicated QA staff on top of it, or anywhere in the middle. Vastly different qualities of work, but the same term - "coding".
So why do we need a term? What difference in action will hearing a different term drive?
On that front, I like the fact that the term "vibe coding" exists because anyone who uses that term unironically has just told me that they care more about the process than the result. Now that is information that changes my actions because it changes how seriously I take them.
Comments
Why do we need a term for any of it, other than "coding". Before AI, I did not need different terms for coding when some devs would cowboy-code buggy slop straight to production vs. a full team doing test-driven development with dedicated QA staff on top of it, or anywhere in the middle. Vastly different qualities of work, but the same term - "coding".
So why do we need a term? What difference in action will hearing a different term drive?
On that front, I like the fact that the term "vibe coding" exists because anyone who uses that term unironically has just told me that they care more about the process than the result. Now that is information that changes my actions because it changes how seriously I take them.