Skip to content
Sondeon

Guides

Guides on software built with AI

What we have learned reviewing software built with AI, written for the person who has to decide. Each guide ends in the service that solves it.

Several printed sheets with tables and a white folder on a pale table, with a gold pen and a bowl of paper clips

Updated on

Guides on software built with AI: what vibe coding is, what breaks, what to review before production and how it is measured, with the sources cited.

  1. What is vibe coding? Meaning, risks, what to check

    What vibe coding means, where the term comes from, whether it is good or bad, the tools used and what to check before AI-written code reaches production.

    Public website review

  2. What are AI agents? Types, examples and risks

    What an AI agent is, how agentic AI differs from a chatbot, the types, business examples and what to review before letting it work with your data.

    Backend and API review

  3. Technical debt: what it is and how to measure it

    What technical debt is, its types and examples, why it grows faster when you build with AI, how it is measured without guessing and where to start.

    Backend and API review

  4. What is data governance? Pillars and framework

    What data governance is, its four pillars, a framework you can check, how it differs from data management and how it is verified in Salesforce and Power BI.

    Database review

  5. Core Web Vitals: what they are and what ruins them

    What Core Web Vitals are, the thresholds for LCP, INP and CLS, how to measure them and what ruins them on a website built with AI, measured in the browser.

    Public website review

Frequently asked questions

What are the risks of putting AI-generated code into production with nobody reviewing it?

The ones you don't see in the demo: exposed keys, excess permissions, unprotected personal data, queries that can't handle real volume and errors that fail silently. These guides explain how each one is measured, with the source of every figure.

Who is going to maintain the code the AI wrote and nobody has read?

Someone who has read it first: maintaining code nobody understands is fixing blind. The technical debt guide explains how to measure what was left half done, and a review tells you what has to be maintained and in what order.

Where do the figures come from?

From published studies, linked inside each guide. A figure without a source is not published.

Request your free meeting

Fill in the form and we email you to set a day and a time. It is 30 minutes to see what you have and what to review first.

What should we control?

We use your details to answer your request, to be able to prove we received it and to protect the form. The privacy policy explains it in detail.