Skip to main content

Frequently Asked Questions

Short, direct answers to what readers ask before they start. Nothing here is aspirational: if something is not built yet, it says so.

What is The Bridge Balance?​

A free, three-stage curriculum that takes a student from zero to spec-driven AI-agent engineering. Spec-driven means you write down what you want built and what must not change before any code is generated; the agent implements inside those boundaries, and you verify its work (not only the result, but how it was built and the core of what it built) and take ownership of it.

The textbook is free forever. An optional paid catalogue is planned alongside it, with Claude Code sub-agents, skills, MCP servers and plugins. The catalogue preview explains these tools; none is available to buy yet. The curriculum itself never charges for content.

Who is it for?​

Anyone who has never programmed. The book starts from zero: nothing is skipped, and nothing is left for you to guess.

No experience is needed to begin. A new word is explained the first two or three times you meet it. After that it becomes a link to the glossary, so a reminder is one tap away. A word that is too big for one sentence gets a short passage of its own before it is used.

Is it really free?​

Yes. The textbook is free with no paywall, no locked chapter, and no email gate, and that holds across the whole curriculum. It is a standing project principle, not a launch offer.

The only paid surfaces are the optional digital products sold alongside the book — Claude Code sub-agents, skills, MCP servers, and plugins. You can complete every stage without buying any of them.

What are the stages?​

A stage is a level of difficulty, and a course inside a stage is one subject.

  • Stage 0 — Introduction to SDE. Your starting point, for a reader who has never programmed. It has two courses: Introduction to Software Engineering, on what programming, the frontend, APIs, the backend and software architecture are, and Introduction to SDE and Basic Terminology, on Spec-Driven Engineering, how it came about, and its words: Code Literacy (reading and judging code), vibe coding and vibe decisioning. It teaches what each thing is and what it is for.
  • Stage 1 — Software and AI Engineering Foundations. Four courses in order: shared foundations, deeper agent engineering, deeper web development, then DevOps, deployment and cloud. You specify what should happen, let AI write code and independently verify its work. The overview explains the depth expected in each course.
  • Stage 2 — Advanced Solution Engineering. Advanced specialisations in engineering, agents, AI use, web work and operations. You use Spec-Driven Engineering for whole solutions, including reliability, security, communication and business decisions.

Both Stage 0 courses and Stage 1's opening Python lessons are available. The later Stage 1 courses and Stage 2 have curriculum outlines; their lessons are not available yet.

Stages 1 and 2 use Stage → Course → Module → Chapter → Lesson, with optional Parts inside a lesson. Each module connects a main subject, its supporting tools and an application. Stage 0 omits modules and goes directly from courses to chapters.

How long does it take, and how many chapters are there?​

The book asks for four hours a day, every day. About 25 minutes of that is the day's lesson, and the rest is practice. A lesson is one page, read from top to bottom in one sitting.

There is no fixed answer to how long the whole book takes, and that is deliberate. The curriculum fixes three stages and their courses, and commits to nothing below those. The topic, title and scope of each chapter are decided when it is written, and the lessons in a chapter vary with what its topic needs. A chapter count or a total-hours figure stated today would be wrong within weeks, so the project never commits to one in advance.

The book is self-paced. The stages lead into one another, and you read one lesson a day. A new word is explained when you meet it and later becomes a glossary link, so you can start in the middle and still look any word up in one tap.

How do the video and text fit together?​

Every chapter starts as text: lessons you can read and return to. Some chapters also get a video lecture, which I record from those lessons. The text is the reference, and the video is the walkthrough built on it.

For Stage 1 and later, the order is:

  1. Learn the topic. I learn it and pass a closed-book check before the lesson is written.
  2. Write and check. The lesson is checked for accuracy and whether a beginner can understand each sentence on the first read.
  3. Apply it. I put the topic to work in real solutions.
  4. Update or record. I update the lesson from that work, or record a video lecture.

Stage 0 comes first as introductory teaching. I read and learn its text, request changes where needed and check it before announcing it.

A chapter can go live with its text before its video exists. It says so on the page, and it counts as a finished milestone rather than an unfinished one.

Is there a community? How do I get help if I'm stuck?​

There is no Discord, no forum, and no other live community channel today. Saying so plainly is more useful than implying one exists.

An AI tutor that answers from the book is planned, but it is not available to readers yet. Accounts, payments and other features that need a signed-in user are also not live.

Until then, the whole book is searchable from the site's search bar, and every chapter is written to stand on its own.

Who maintains this, and how?​

I maintain the book. The learning and checking process above guides its lessons, and the curriculum outlines distinguish planned material from what you can read now.

There is no editorial board and no release schedule. Chapters land when they are ready, and the changelog records what shipped and when.

Can I contribute, or suggest a change?​

There is no public contribution process yet. I keep the working repository private. If a way to submit changes opens up, I will explain it here.

If a way to contribute opens up, the changelog will say so.