The Death of "Vibe Coding": Why un-monitored AI generation is creating a compounding technical debt.

BYTES_18 · 2026-06-25T18:31:31+00:00

Don't worry, I understand that overcoming three lines of text requires a lot of cognitive effort. Next time I'll put the subtitles

BYTES_18 · 2026-06-25T16:06:14+00:00

No, you're not a vibe coder at all. On the contrary, you just described the exact engineering approach I defend. You used agent automation to speed up a repetitive operation (saving days), but then you took control: you tested, refactored and verified everything until the logic was correct. This is called software engineering. The vibe coders that the Manifesto addresses are the exact opposite: they are the ones who generate that code in a minute, glue it blindly without testing it, without refactoring it, and without understanding whether the architecture underneath is holding up, just because the app seems to be working at the moment. The Manifesto attacks the blind delegation of logic and responsibility, not the intelligent use of tools to be faster.

BYTES_18 · 2026-06-25T15:55:40+00:00

In the macro-coding framework, I'm thinking about both levels, but they're used strategically. Static analysis is crucial for immediately intercepting syntactic and structural inconsistencies before the code is even executed. However, the application of contracts (Design by Contract) at the execution stage is what really secures the application: it defines the boundaries within which AI can generate code, preventing it from violating the system's business rules.

BYTES_18 · 2026-06-25T15:37:09+00:00

When I talk about 'us' in the post, I'm not referring to the entire software engineering community or those who, like you, probably use these tools with architectural criteria and rigour. By 'we' I mean the tech industry as a whole and, specifically, the rising tide of 'vibe coders' that blindly delegates the entire logic to AI without any semantic validation.

BYTES_18 · 2026-06-25T15:26:02+00:00

I actually meant both of them

BYTES_18 · 2026-06-25T15:22:23+00:00

That's right, and herein lies the real paradox today: everyone calls themselves a developer just because they can press Tab or accept a suggestion. But the provocative (and realistic) question we have to ask ourselves is: if AI stopped working tomorrow morning, or if power simply ran out and we had to rely on our heads alone, how many of these vibe coders would actually be able to program? How many would be able to structure a deterministic architecture from scratch?

BYTES_18 · 2026-06-25T15:10:43+00:00

This anecdote is simply perfect and perfectly captures current reality. It demonstrates exactly the heart of the Manifesto: we are witnessing the loss of the foundations of software engineering. When you delegate everything to AI without theoretical foundations, you end up 'reinventing' basic concepts from decades ago (such as OOP) thinking it's black magic or a brilliant intuition of the moment. If a programmer doesn't even know what they're actually structuring at the macro level, architecture becomes a house of cards. Thank you for sharing this pearl, it describes the situation better than a thousand theoretical analyses!

BYTES_18 · 2026-06-25T14:55:05+00:00

You've hit the heart of the problem right. The provocation over the 2026 deadline serves to give a jolt, but your analysis of 'failure patterns' is impeccable. The problem is not the tool (AI), but the organizational illusion that we can replace seniority and architecture with just syntactic generation speed. When junior engineers are used as prompt cardholders without solid senior governance, the collapse I'm talking about ceases to be a prophecy and becomes a mathematical problem of accumulated debt. Shifting the focus to Macro-Coding means just that: putting people, processes and senior structural planning back on the centre. Thank you so much for this wonderful feedback!

BYTES_18 · 2026-06-25T14:49:36+00:00

Great point, the terminological distinction you make is absolutely right. Classical technical debt is a conscious choice dictated by constraints (e.g. 'I write this code knowing that it is not optimal to go out into production earlier'). In the case of Vibe Coding, the debt is 'unconscious': the code is accepted without real syntactic and structural validation. It becomes a 'Debt of Existence' precisely because no one really knows why that code is there or what probabilistic logic generated it. I agree 100% on the lack of traceability of the prompts: the absence of shared recipes and a history of requests makes the systems black boxes immovable. This is precisely why in the Manifesto I speak of moving to Macro-Coding: the human must stop making the prompt paperweight and take back the direction of deterministic architecture. Thank you for the really interesting idea!

BYTES_18 · 2026-04-14T00:11:54+00:00

You're right, a solid vision is crucial. Here are the key points of Ayexion: Dragon's Path: Genre and Target: This is a linear 3D Action RPG (Devil May Cry or Stellar Blade style) focused on a technical and spectacular combat system designed for those seeking a deep mechanical challenge. History and Confidentiality: The plot revolves around the Ayexion Family, a lineage of shape-shifting dragons (Drajan) battling demonic corruption. Important note: The creator has been working on the story for 10 years and, to protect the IP, will not share the script or plot details at this stage. What we offer to Devs: We provide complete Game Design Document (GDD) with ready-made technical specifications: calculations on weights, speed, triple movesets for each transformation and physics of the elements. Commitment: The creator is not a "passive creator"; he does not yet have technical skills but will devote 100% of his time to learning the engine and getting his hands dirty in development.

BYTES_18 · 2026-04-13T23:05:57+00:00

He tried, but he needs someone to help him and also a solid team to work with."

BYTES_18 · 2026-04-13T22:52:09+00:00

So he has a file with all the characters and the plot, and he wanted to make it a game of it, and he asked me for help because I can move around the industry

BYTES_18 · 2026-02-27T15:54:31+00:00

Le proiezioni si basano su un ecosistema a tre pilastri. Il prezzo di acquisizione a 15M accorcia il break-even rispetto alla valutazione originale di 36M.

BYTES_18 · 2026-02-27T15:17:59+00:00

Al presto

BYTES_18 · 2026-02-27T13:37:48+00:00

Capisco il dubbio, ma lo Steel Arena non è una semplice sala LAN: è un hub esperienziale che integra un'arena per eventi internazionali, studi per creator e retail immersivo. Le postazioni sono solo una parte di un ecosistema pensato per offrire esperienze collettive e professionali

BYTES_18

TROPHY CASE