Journal
Journal: vibe coding
On this topic, 13 articles from the journal, from practical guides to behind the scenes of the product.
AI breaks my application with every change: why a method beats a better model
You request one fix and get three failures. The reflex is to switch tools, then models, then tools again. Those who escaped the loop describe a writing habit costing one line per request.
Read the article
Exposed customer data: a two-minute test for an AI-created application
Your application displays a login screen, so your customer data is protected. Providers repairing these applications describe the opposite across three different samples. Three checks you can perform tonight, and three questions for whoever builds it.
Read the article
Building an application without knowing how to code in 2026: four routes
No-code, prompt generator, coding assistant, agent team: four ways to have software written without writing it yourself. They do not cost the same, and above all they do not leave the same things in your hands when you stop paying.
Read the article
Why agency prices have not followed the fall in AI costs
What cost $60 per million tokens in late 2021 now costs between $0.06 and $0.40 at equivalent performance, a reduction of 150 to 1,000 times. Meanwhile, a developer's average daily rate in France remains around €629. Someone is keeping that margin.
Read the article
AI makes experts slower: why approval must be an architecture, not a chore
The METR study measured experienced developers as 19% slower with AI, while they believed they were 20% faster. Review and verification consumed the gain. The problem is not review: it is where we put it.
Read the article
The 5 AI development traps nobody tells you about
Drift without specifications, false green lights, opaque credits, disposable code and dependence: five documented traps encountered in our own measurement campaigns, and a safeguard for each.
Read the article
A prototype in an evening, a product in a week: the real boundary
AI tools make spectacular prototypes and viable products possible. Between them lie three gaps invisible on screen: written rules, tests that prove, and versions that can be restored.
Read the article
Tests first, and woe to the agent that changes them: TDD imposed on machines
TDFlow reaches 88.8% on SWE-Bench Lite when tests are supplied before code. At Maestro, tests have been written BEFORE each story since July, with one simple rule: an agent modifying a test, even a pre-existing one, is flagged.
Read the article
No-code or AI: should you still learn Bubble in 2026?
No-code promised building without coding, at the cost of learning an editor. AI shifts the promise: nothing left to assemble yourself, requirements to direct, and standard code you own.
Read the article
Vibe coding explained to people who will never code
Describe what you want and let AI code it: vibe coding won over developers in 2025. For a non-developer, one thing is missing: a place to record decisions.
Read the article
Lovable, Bolt, v0 or Maestro: which AI tool should you choose for your application?
Compare project preparation, construction, publishing and code handover. A reading of documented capabilities to help you choose for your needs, including Maestro's limitations.
Read the article
Your specifications will soon be worth more than your code
AI makes code abundant. Understanding becomes the scarce resource: knowing what you wanted to build, and why. Three levels of maturity are emerging.
Read the article
Directing AI agents without knowing how to code: what has changed
AI has been able to write code for a while. What is new: a non-technical person can now direct it.
Read the article