---
title: "Discussion on \"AI Coding Tip 042 - Stop AI Cowboy Vibe Coding\" | Hashnode"
description: "Discussion on \"AI Coding Tip 042 - Stop AI Cowboy Vibe Coding\". The spec asked for one change, and the AI shipped fourteen."
url: "https://hashnode.com/posts/ai-coding-tip-042-stop-ai-cowboy-vibe-coding/6b00be7a599593b7b909e7f8"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [AI Coding Tip 042 - Stop AI Cowboy Vibe Coding](https://maximilianocontieri.com/ai-coding-tip-042-stop-ai-cowboy-vibe-coding?utm_source=hashnode&utm_medium=feed)

The spec asked for one change, and the AI shipped fourteen.

4h ago · 8 min read · maximilianocontieri.com  
Read the article

## Written by

[Maxi Contieri](https://hashnode.com/@mcsee)

@mcsee · Buenos Aires

  
[View profile](https://hashnode.com/@mcsee)

Software Engineer

I’m a senior software engineer loving clean code, and declarative designs. S.O.L.I.D. and agile methodologies fan.

## Responses 1

Markdown supported · ⌘↵ to post

[Macro8n](https://hashnode.com/@macro8n)

[1h ago](https://hashnode.com/posts/ai-coding-tip-042-stop-ai-cowboy-vibe-coding/6b00be7a599593b7b909e7f8/comment/6b00e8b9e8bff92d9985e1e6)

A practical guardrail for this kind of scope creep: ask the model to name the files and behaviors it intends to change before editing, then compare the final diff against the requested acceptance criteria. Any extra change needs a reason of its own. A short non-goals list helps too. In your experience, does scope drift show up in the plan or only when you inspect the diff?
