Mantenere il codice manutenibile
Organizzi il codice affinché possa modificarlo anche in futuro
Mantenere il codice manutenibile è una lezione Vibe Coding gratuita su CoddyKit. Questa è la lezione 3 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento Vibe Coding, e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso Vibe Coding include 4 lezioni in totale.
Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.
Code Is Read More Than It's Written
AI can generate a working app in minutes. But six weeks later, when you ask it to add a feature, messy code makes everything slower — for both you and the AI. Maintainable code is code that future-you (and future-AI) can change without fear.
This lesson is about keeping a vibe-coded project clean enough to grow.
Clear Names Beat Clever Code
The single highest-impact habit: good names. A function called calculateMonthlyTotal tells you what it does; doStuff2 tells you nothing.
AI sometimes picks lazy names. Just ask it to rename for clarity.
// Hard to follow
function d(x, y) { return x - (x * y / 100); }
// Self-explaining
function applyDiscount(price, percentOff) {
return price - (price * percentOff / 100);
}
console.log(applyDiscount(100, 20));Small Functions, One Job Each
A function that does five things is hard to understand and risky to change. Break work into small functions that each do one thing. When you change one, you won't accidentally break the others.
AI is happy to refactor when asked.
Refactor this function so each step is its own small, well-named function. Don't change behavior. Here it is:
function checkout(cart) {
// calculates totals, applies discount, charges card, sends email...
<paste the big function>
}
Return the refactored version with a short note on what each function does.Organize Files by Purpose
A single 3000-line file is a nightmare. Group related code into folders: things about users in one place, payments in another, UI in another. You'll find code faster, and so will the AI.
Ask AI to propose a structure before you reorganize.
My project is one big app.js file. Suggest a clean folder structure for a small web app with users, products, and checkout. Show me which functions go in which file, and explain the reasoning. Don't move anything yet — just propose the layout.Don't Repeat Yourself
When the same logic appears in three places, a bug fix means three edits — and you'll forget one. Pull repeated logic into a single shared function. This is the DRY principle: Don't Repeat Yourself.
AI loves to copy-paste, so this one needs your eye.
// Repeated formatting in many places
const a = '$' + price1.toFixed(2);
const b = '$' + price2.toFixed(2);
// One source of truth
function formatPrice(value) {
return '$' + value.toFixed(2);
}
console.log(formatPrice(9.5), formatPrice(120));Comment the Why, Not the What
Good code explains what it does through clear names. Comments should explain why — the reasoning that the code can't show. AI often over-comments the obvious; trim those and keep the meaningful ones.
// Noise: the code already says this
let count = 0; // set count to zero
// Useful: explains a non-obvious decision
// Stripe rounds to cents, so we store integers to avoid float errors
const amountInCents = Math.round(dollars * 100);A README So You Don't Forget
Three months from now you won't remember how to run your own app. A README file captures the essentials: what the project is, how to install it, how to run it, and what the environment variables mean.
Have AI generate one from your code.
Read my project and write a README.md with: a one-line description, setup steps (install + run commands), required environment variables and what each is for, and how to run the tests. Keep it short and skimmable.Keep a Consistent Style
Mixed quotes, random indentation, and inconsistent spacing make code harder to read. A formatter like Prettier auto-fixes all of that, and a linter like ESLint flags risky patterns.
You don't configure these by hand — ask AI to set them up.
Set up Prettier and ESLint for this JavaScript project. Add a "format" and a "lint" script to package.json, sensible default configs, and tell me the one command to auto-format the whole codebase.Refactor in Small, Safe Steps
The biggest maintainability trap is rewriting everything at once and breaking the app. Instead, clean up in small steps — and lean on the tests you wrote earlier to confirm nothing broke after each change.
Tell the AI to go incrementally.
Refactor this module for readability, but do it in small steps. After each change, keep the behavior identical so my existing tests still pass. List the steps you'd take in order before changing anything.Avoid Magic Numbers
A raw number like 0.07 buried in code is a mystery. Give it a name. Named constants make the code readable and mean you change the value in one place.
// Magic number — what is 0.07?
function withTax(price) { return price * 1.07; }
// Clear and easy to update
const TAX_RATE = 0.07;
function withTax(price) {
return price * (1 + TAX_RATE);
}
console.log(withTax(100));Maintainable Code Helps the AI Too
Here's the payoff specific to vibe coding: clean, well-named, well-organized code makes the AI's future answers better. When the AI can understand your structure, its edits are more accurate and it breaks fewer things.
Maintainability isn't just for humans — it's how you keep your AI partner effective as the project grows.
Quick Check
You notice the same price-formatting logic copy-pasted in seven different files. Following good maintainability habits, what should you do?
Recap: Build to Last
Maintainable code is what lets a vibe-coded project keep growing. Your habits: clear names, small single-purpose functions, organized files, DRY shared logic, meaningful comments, a README, consistent formatting via Prettier/ESLint, and small safe refactors backed by tests.
And remember: clean code makes the AI better at helping you next time. Next up: performance and cost — keeping your app fast and your bills sane.
Domande Frequenti
La lezione «Mantenere il codice manutenibile» è gratuita?
Sì — il testo completo di «Mantenere il codice manutenibile» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso Vibe Coding, passa a CoddyKit PRO. Il corso Vibe Coding include 4 lezioni in totale.
Cosa imparerò in «Mantenere il codice manutenibile»?
Organizzi il codice affinché possa modificarlo anche in futuro Eserciti Vibe Coding con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.
Ho bisogno di esperienza per iniziare Vibe Coding?
Non è richiesta alcuna esperienza precedente. Vibe Coding su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 3 di 4.
Quanto tempo richiede la lezione «Mantenere il codice manutenibile»?
La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.
Posso scrivere ed eseguire codice in questa lezione Vibe Coding?
Sì. Ogni lezione Vibe Coding include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.
Tutte le lezioni di questo corso
- Aggiungere test con l'IA
- Nozioni di base sulla sicurezza per il codice IA
- Mantenere il codice manutenibile
- Prestazioni e costi