Johnder Perez

Track 3 of 4 · 6 short steps

Writing Code That Lasts


Goal: Write code that other people, future you, and future AI sessions can understand, test and safely change.

Why this matters

AI can generate a 900-line file in seconds. The hard part is changing it next month without breaking three other things. Software engineering is the craft of keeping a codebase easy to change. It matters even more with AI, because AI tools work best on small, clearly organized, well-tested code.

The steps

Each step is a 2-minute read with a quick check at the end.

  1. Step 1

    Version control with Git

  2. Step 2

    Separation of concerns and layers

  3. Step 3

    SOLID and design patterns, in plain English

  4. Step 4

    Code smells and technical debt

  5. Step 5

    Testing: unit, integration, end-to-end

  6. Step 6

    Test-driven development (TDD)

Start step 1 →

Try it

Challenge: Spot the bug

Click the line with the bug.

AI mistakes to watch for

Tip: paste a file into your AI tool and ask, "Check this for each of these issues and explain any you find." Then verify what it says yourself.

Milestone checklist

Your ticks are saved in this browser only.

Reading & free resources

← Thinking in Algorithms & Data Next: Building for Scale →