The honest test

1. Five questions

Before you read on, here are five honest questions. Answer them in your head. No one's grading.

1. Do you want a clear picture of what software engineering looks like now, not what it looked like five years ago?
2. Are you okay with reading instead of building? This course has no exercises and no projects.
3. Can you sit with the idea that some things you've heard about AI in engineering are wrong, including some things you might believe today?
4. Do you want a calibration, not a credential? You'll finish with a better map of the field, not a certificate.
5. Are you willing to think about whether this career is right for you, even if the honest answer turns out to be no?

If most of those are yes, this course is for you. Read on.

2. If they're mostly no

That's fine. Some honest pointers, depending on which part didn't fit.

If you want to build something instead of read about the field, start with [[tutorial-to-engineer]]. It's also free, and it's about how to learn programming without wasting months.

If you want hands-on prompt practice with real engineering examples, [[vibe-to-spec]] is the next free course. It's structured around worked examples, and you'll write prompts as you go.

If you already write code and want to go deep on AI design patterns for production systems, look at [[api-to-architecture]]. That one isn't free, and it assumes you've shipped code before.

If you want a job at a specific company and you're already mid-career, [[question-to-offer]] is the system design and interview prep course. Also paid, also assumes experience.

3. What this course will and won't promise

It won't promise you a senior engineering job tomorrow. It won't promise you'll be hired off the back of reading it. It won't promise the field is easy now that the model exists.

What it will give you: a clear, honest, current view of how the work has changed, what's worth learning, and what kinds of engineers companies actually want in 2026.

4. Who's welcome

Everyone who's serious. That's the whole bar.

You can be fifteen or fifty. You can be reading this on your phone between shifts at a job you'd like to leave. You can be a CS student in your second year. You can have shipped code for a decade and feel like the ground moved under you. You can have never opened a terminal.

Serious means you're willing to read carefully and update your beliefs when the evidence calls for it. That's all this course needs from you.

5. The next chapter

Chapter 1 is the comparison chapter. It's where the picture sharpens.

Start there.