Devibecoding as a Service? 💡

Apparently my brain won't stop thinking about vibecoding today so here is another one.

🚀 In my previous posts I defined vibecoding as code nobody fully understands, and devibecoding as the process of making it yours. But what if you can't or don't want to do that yourself?

🏢 I think there's a business model emerging here. More and more startups and small companies vibecode their MVPs. Some of those actually get traction. And suddenly you have a prototype that works, has users, maybe even revenue — but the code underneath is a black box nobody on the team truly understands.

🔧 Enter devibecoding as a service. A spectrum from self-help to full takeover:

⚡ Tools that help you understand and restructure your own vibecoded codebase
⚡ Consulting and code audits that identify the critical gaps
⚡ Full transformation — taking a vibecoded prototype and turning it into a maintainable business application

🤔 This isn't entirely new — agencies have always rescued messy codebases. But the scale could be different. If vibecoding lowers the barrier to building software, the number of prototypes that need "growing up" will explode.

💬 Think of it as the natural next step: vibecoding creates, devibecoding matures. And there might be a whole industry in between.

Would you pay for devibecoding as a service? Or is "just rewrite it properly" always the better answer?

#SoftwareDevelopment #AI #Vibecoding #Devibecoding #StartupLife #CodeQuality #BusinessModel

Devibecoding 🔧

In my last post I defined vibecoded code as code nobody on your team has fully understood. But what happens when you take that code and make it yours?

I think we need a term for this: devibecoding.

💻 Devibecoding is the process of taking code you don't fully grasp — whether AI generated or not — and systematically working through it until you truly own it. Understanding it, restructuring it, making it maintainable.

🧠 This is not just code review. It's a mix of reverse engineering, refactoring and deep comprehension — without being able to ask the original author about their intent. Because there was no human author.

💬 Someone in the replies to my last post described exactly this: putting in the effort to understand and reformat AI output until it becomes their code. That's devibecoding in practice.

🚀 And here is my take: this will become its own discipline. With its own tools, its own best practices, maybe its own specialists. Think tools that don't just lint but explain. That visualize where your understanding gaps are. Possibly even AI helping you understand AI code — ironic but inevitable.

⚡ The more vibecode exists in the world, the bigger the need for people who can devibecode it.

What do you think — is this already part of your workflow? And what tooling would help you most? 🔍

#SoftwareDevelopment #AI #Vibecoding #Devibecoding #CodeQuality #DevLife #Refactoring

🤖 Everyone talks about vibecoding but most definitions focus on how the code was created. I think that misses the point.

My take: vibecoded code is code that nobody on your team has fully understood. It doesn't matter if an AI wrote it, a junior dev copied it from Stack Overflow, or a senior dev hacked it together at 2am. If nobody has truly reviewed and comprehended it — it's vibecode.

That distinction matters because it shifts the conversation from "did you use AI?" to "do you actually know what this does?" 🔍

This also means: code that an AI generated but you thoroughly reviewed and understood is NOT vibecode. The tool doesn't define the category — your level of understanding does.

Why does this matter? Because it changes the risk assessment entirely. Using AI to write code you then deeply review is just a productivity tool. Shipping code you don't fully grasp is a conscious risk decision — sometimes justified, sometimes not.

Do you agree with this definition? Or would you draw the line somewhere else?

#SoftwareDevelopment #AI #Vibecoding #CodeQuality #DevLife

AI Can Write Code, But It Can’t Debug Without Context

Large Language Models (LLMs) are often marketed as the ultimate productivity boost for developers: “Write code faster! Debug with AI! No more manual work!” After a recent experience, I can confirm that LLMs are incredibly useful for writing and even structuring code (I’ll write about this probably in a later blog post).

But when it comes to debugging, one should make really sure that the tool has access to all the relevant context (and don’t disable your brain). But .. let’s see, what happened:

Since a couple of days (uhm .. nights mostly, after work), I was writing a web application. The copilot-experience was very good and it really helped tremendously. I never really ran into a situation where I had to debug. And I was curious when (if?) I’d run into that – and how things turn out then.

[…]

Another week, and let me ask, did you ever had this super worker engineer in your team that really wanted to code? The first one to appear in the office, and the last one to leave, every day... So maybe this could be a good read for you

https://jeferson.me/blog/2026/03/20/john-is-an

#AI #Blog #Code #CodeQuality #Engineering #John #Management #Quality #Software #TechnicalDebt #VibeCoding

AI Agents Ship Bugs Faster Than You Can Fix Them

What happens when you let AI agents build your product — and log every mistake they make

https://mistaike.ai/blog/ai-agents-bugs

#Ai #Codequality #Mcp #Lessonslearned

AI Agents Ship Bugs Faster Than You Can Fix Them

What happens when you let AI agents build your product — and log every mistake they make

https://mistaike.ai/blog/ai-agents-bugs

#Ai #Codequality #Mcp #Lessonslearned

AI Agents Ship Bugs Faster Than You Can Fix Them

What happens when you let AI agents build your product — and log every mistake they make

https://mistaike.ai/blog/ai-agents-bugs

#Ai #Codequality #Mcp #Lessonslearned

via @dotnet : Accelerating .NET MAUI Development with AI Agents

https://ift.tt/xiAcVos
#dotnetMAUI #AI #AIAgents #Developers #SoftwareDevelopment #MAUI #DotNet #GitHubCopilotCLI #Automation #CodeQuality #Testing #TestAutomation #PrReview #WriteTestsAgent #TryFix…

AI Agents Ship Bugs Faster Than You Can Fix Them

What happens when you let AI agents build your product — and log every mistake they make

https://mistaike.ai/blog/ai-agents-bugs

#Ai #Codequality #Mcp #Lessonslearned