{"id":11099,"date":"2026-06-04T06:39:29","date_gmt":"2026-06-04T12:39:29","guid":{"rendered":"https:\/\/attentionmedia.io\/?p=11099"},"modified":"2026-06-04T06:39:29","modified_gmt":"2026-06-04T12:39:29","slug":"how-to-make-vibe-coding-sustainable-inside-the-enterprise","status":"publish","type":"post","link":"https:\/\/attentionmedia.io\/?p=11099","title":{"rendered":"How to make vibe coding sustainable inside the enterprise"},"content":{"rendered":"
\"a<\/div>\n

Vibe coding<\/a> enables more people to build software using natural-language prompts rather than traditional programming. That speed accelerates experimentation and delivery across marketing technology teams.\u00a0 But it\u2019s also a high-reward, high-responsibility model<\/a>. Organizations still need to secure, maintain, validate, and document the software they ship, regardless of how the code was generated.<\/p>\n

While software communities already use frameworks to manage distributed development and shared accountability, enterprises adopting vibe coding need operational principles of their own. Using AI to vibe-code software shifts more responsibility to governance, review, and long-term maintenance. Humans are still accountable for evaluating deliverables and maintaining the code over time.<\/p>\n

That accountability includes ensuring the code is secure, performant (free of major bugs and able to run on existing infrastructure), compatible with evolving platforms the code interacts with, and up to date with changing software standards and practices.<\/p>\n

It may seem counterproductive to complicate a development approach, but organizations must consider the liability of using weak code. For example, explaining that something was vibe-coded isn\u2019t a defense when addressing a data breach. Will AI platforms indemnify the organization?<\/p>\n

This risk is already materializing. Recently, security researcher Dor Zvi shared with Wired that his team found vibe-coded apps exposed sensitive information<\/a>, including \u201cmedical information, financial data, corporate presentations, and strategy documents, as well as detailed logs of customer conversations with chatbots.\u201d<\/p>\n

From a personnel perspective, this shifts human responsibility from writing code to reviewing, validating, and governing it. Organizations need workflows that involve humans to ensure software is robust and secure.<\/p>\n

<\/a><\/p>\n

\n
\n
\n Your customers search everywhere. Make sure your brand shows up<\/span>.\n <\/div>\n

\n The SEO toolkit you know, plus the AI visibility data you need.\n <\/p>\n<\/div>\n

\n Start Free Trial<\/span>\n <\/div>\n
\n
Get started with<\/div>\n

\"Semrush\n <\/p><\/div>\n<\/div>\n

<\/p>\n

Making vibe coding sustainable<\/h2>\n

Sometimes great promise brings great chaos. Fortunately, several principles enhance the promise while mitigating the chaos.<\/p>\n

Intentionality over velocity<\/h3>\n

AI tools can quickly generate code that would take humans much longer to develop. This accelerated speed exacerbates an existing challenge: understanding the why when figuring out the how and what.<\/p>\n

While it\u2019s ideal for everyone involved in a software project to understand the ultimate goals, purpose, and needs of a project or task, the deliberation at human speed can sometimes help refine the why before delivery. Many related frameworks, such as agile and waterfall project management methodologies, facilitate requirements gathering. However, when something arrives within minutes, much of that deliberation disappears.<\/p>\n

That makes establishing a clear intention through a thoroughly documented and evaluated intention statement critical. Granted, vibe coding allows rapid iteration, but it can easily devolve into unproductive wheel-spinning.<\/p>\n

Clearly defining the intention enables teams to evaluate whether the software remains maintainable over time. This occurs throughout acceptance, continual monitoring, and eventual code updates for long-term upkeep.<\/p>\n

Auditability as a first-class concern<\/h3>\n

Audits can assist with tracing intention to execution.<\/p>\n

Organizations that vibe code need a robust documentation process to track what led to a software deliverable. This includes tracking prompts, platform, and model, production date, and humans involved in review and evaluation. A prompt log is an important artifact and deliverable.<\/p>\n

This documentation helps identify the ongoing ownership responsibilities of vibe-coded deliverables. Beyond the responsibilities, it helps assign those responsibilities to individuals.<\/p>\n

Incremental trust, not blanket acceptance<\/h3>\n

AI-generated code needs the same amount of validation as human-generated code. This includes QA, user acceptance testing (UAT), peer review, security scanning, and more. This remains important even if guardrails and universal requirements are included in code generation.<\/p>\n

Vibe coding doesn\u2019t remove or reduce the need for validation. Given the speed at which AI tools generate code, validation is even more important.<\/p>\n

This need becomes even clearer because many people creating prompts for code generation lack a programming background. For instance, the person prompting the code might lack the knowledge to add the necessary security-specificity to their prompt.<\/p>\n

Domain boundary respect<\/h3>\n

Within enterprise tech stacks, boundaries often limit where certain data can reside, for how long, and who can access it. Other standards designate who really needs access to certain data, including who shouldn\u2019t have access. These boundaries must remain.<\/p>\n

Organizational personnel and the AI tools they use must observe and obey these boundaries. Failing to respect these boundaries isn\u2019t a bug. It\u2019s likely a failure in regulatory compliance and risk mitigation.<\/p>\n

This relates to what Allen Martinez calls a shadow ledger<\/a> of liabilities accumulated when organizations use AI agents. It includes a governance gap (no formal rules about how AI can act), an accountability gap (inability to tie agent output to rules), and an identity gap (inconsistent agent voice across stakeholders and audiences).<\/p>\n

Legibility as a deliverable<\/h3>\n

While this may seem obvious, it matters. In vibe coding, as Google Gemini stated, the programmer\u2019s role shifts from writer to editor. They need to understand what the code <\/a>is doing. A business stakeholder sign-off from a UAT perspective<\/a> isn\u2019t sufficient.<\/p>\n

As a principle, this helps ensure the code is secure, performant, and error-free. It also helps ensure the code doesn\u2019t conflict with other code it affects while still meeting requirements. This further supports sustainable upkeep.<\/p>\n

Deprecation hygiene<\/h3>\n

Whether code is human-generated or vibe-coded, examining existing code when creating new code matters.<\/p>\n

As codebases evolve, they understandably accumulate features and functions. In many cases, a piece of code may have met needs and requirements at one time, but those needs and requirements frequently change or retire. Over time, that can make the codebase unwieldy and difficult to maintain.<\/p>\n

Further, workarounds or shortcuts sometimes meet a specific need quickly. Tech debt has a purpose, but creating it is far easier than deprecating it later. That shortcut eventually bears the burden of infrastructure, making it far harder to resolve, given the interconnected dependencies.<\/p>\n

When adding code, evaluating what code is suitable for deletion becomes equally important. Vibe coding should help consolidate and replace solutions, not unnecessarily layer on top of existing code.<\/p>\n

Feedback loops back into prompts<\/h3>\n

When vibe-coded output fails reviews and standards, that isn\u2019t necessarily wasted effort. It\u2019s an iteration. A failed test signals that prompt templates and guardrails can be improved. This perspective fosters continual improvement. That can make any organization\u2019s vibe-coding process more efficient and effective.<\/p>\n

A sustainable workflow for vibe coding<\/h2>\n

These principles can help develop workflows. Here\u2019s a sample:<\/p>\n

\n\n\n\n\n\n\n\n\n\n
Phase<\/strong><\/td>\nObjective<\/strong><\/td>\nKey deliverable \/ artifact<\/strong><\/td>\n<\/tr>\n
1. Intention<\/strong><\/td>\nDefine the why and how. Establish data boundaries and expected outcomes before prompting begins.<\/td>\nIntention statement (Problem definition and risk assessment)<\/td>\n<\/tr>\n
2. Execution<\/strong><\/td>\nRapid iteration and code generation. Use AI to build features while documenting the \u201cconversation.\u201d<\/td>\nPrompt log (record of models, seeds, and key prompts used)<\/td>\n<\/tr>\n
3. Audit and validation<\/strong><\/td>\nVerify that the code actually works. Perform QA, UAT, and security scans to ensure it meets business requirements and won\u2019t break existing stack components.<\/td>\nValidation report (passing test cases and security clearance)<\/td>\n<\/tr>\n
4. Legibility review<\/strong><\/td>\nShift from writer to editor. A human engineer reviews the code to ensure it can be maintained by others.<\/td>\nAnnotated codebase (human-verified documentation)<\/td>\n<\/tr>\n
5. Hygiene check<\/strong><\/td>\nPrevent \u201ccode bloat.\u201d Identify whether this new code replaces older scripts or if legacy debt can be deleted.<\/td>\nDeprecation list (identifying code for removal)<\/td>\n<\/tr>\n
6. Optimization<\/strong><\/td>\nClose the loop. Use the successes and failures of this build to sharpen your future prompts.<\/td>\nUpdated prompt templates (institutional knowledge)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

Vibe-coding principles serve a purpose<\/h2>\n

One of the most important promises of vibe coding is its ability to speed up software development. It also allows people without a technical background to develop their own solutions.<\/p>\n

While vibe coding accelerates execution, it doesn\u2019t lessen human accountability. If software falters, its production method isn\u2019t a defense when conversion rates drop, or attackers strike.<\/p>\n

While these principles may affect some of the speed-and-vibe coding promises, they help ensure that software ultimately meets expectations and eases upkeep.<\/p>\n

Disclosure:<\/em><\/strong> My idea is to establish principles for vibe coding. Claude generated the principles, which I explore and explain using my own thoughts and experience. Gemini reviewed my work.<\/em><\/p>\n

The post How to make vibe coding sustainable inside the enterprise<\/a> appeared first on MarTech<\/a>.<\/p>","protected":false},"excerpt":{"rendered":"

Vibe coding enables more people to build software using natural-language prompts rather than traditional programming. That speed accelerates experimentation and delivery across marketing technology teams.\u00a0 But it\u2019s also a high-reward, high-responsibility model. Organizations still need to secure, maintain, validate, and document the software they ship, regardless of how the code was generated. While software communities … <\/p>\n

Read more “How to make vibe coding sustainable inside the enterprise”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-11099","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"featured_media_urls":{"thumbnail":["https:\/\/martech.org\/searchengineland.com\/wp-content\/seloads\/2025\/11\/semrush-one.webp",0,0,false],"medium":["https:\/\/martech.org\/searchengineland.com\/wp-content\/seloads\/2025\/11\/semrush-one.webp",0,0,false],"medium_large":["https:\/\/martech.org\/searchengineland.com\/wp-content\/seloads\/2025\/11\/semrush-one.webp",0,0,false],"large":["https:\/\/martech.org\/searchengineland.com\/wp-content\/seloads\/2025\/11\/semrush-one.webp",0,0,false],"1536x1536":["https:\/\/martech.org\/searchengineland.com\/wp-content\/seloads\/2025\/11\/semrush-one.webp",0,0,false],"2048x2048":["https:\/\/martech.org\/searchengineland.com\/wp-content\/seloads\/2025\/11\/semrush-one.webp",0,0,false],"inspiro-featured-image":["https:\/\/martech.org\/searchengineland.com\/wp-content\/seloads\/2025\/11\/semrush-one.webp",0,0,false],"inspiro-loop":["https:\/\/martech.org\/searchengineland.com\/wp-content\/seloads\/2025\/11\/semrush-one.webp",0,0,false],"inspiro-loop@2x":["https:\/\/martech.org\/searchengineland.com\/wp-content\/seloads\/2025\/11\/semrush-one.webp",0,0,false],"portfolio_item-thumbnail":["https:\/\/martech.org\/searchengineland.com\/wp-content\/seloads\/2025\/11\/semrush-one.webp",0,0,false],"portfolio_item-thumbnail@2x":["https:\/\/martech.org\/searchengineland.com\/wp-content\/seloads\/2025\/11\/semrush-one.webp",0,0,false],"portfolio_item-masonry":["https:\/\/martech.org\/searchengineland.com\/wp-content\/seloads\/2025\/11\/semrush-one.webp",0,0,false],"portfolio_item-masonry@2x":["https:\/\/martech.org\/searchengineland.com\/wp-content\/seloads\/2025\/11\/semrush-one.webp",0,0,false],"portfolio_item-thumbnail_cinema":["https:\/\/martech.org\/searchengineland.com\/wp-content\/seloads\/2025\/11\/semrush-one.webp",0,0,false],"portfolio_item-thumbnail_portrait":["https:\/\/martech.org\/searchengineland.com\/wp-content\/seloads\/2025\/11\/semrush-one.webp",0,0,false],"portfolio_item-thumbnail_portrait@2x":["https:\/\/martech.org\/searchengineland.com\/wp-content\/seloads\/2025\/11\/semrush-one.webp",0,0,false],"portfolio_item-thumbnail_square":["https:\/\/martech.org\/searchengineland.com\/wp-content\/seloads\/2025\/11\/semrush-one.webp",0,0,false]},"_links":{"self":[{"href":"https:\/\/attentionmedia.io\/index.php?rest_route=\/wp\/v2\/posts\/11099","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/attentionmedia.io\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/attentionmedia.io\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/attentionmedia.io\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/attentionmedia.io\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=11099"}],"version-history":[{"count":0,"href":"https:\/\/attentionmedia.io\/index.php?rest_route=\/wp\/v2\/posts\/11099\/revisions"}],"wp:attachment":[{"href":"https:\/\/attentionmedia.io\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=11099"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/attentionmedia.io\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=11099"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/attentionmedia.io\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=11099"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}