The goal is not for Emily to become someone who can write software.
The goal is for Emily to become someone who can imagine a useful digital system, explain how it should work, evaluate different designs, collaborate effectively with humans and AI to build it, and confidently evolve it over time.
This apprenticeship develops engineering judgement rather than programming proficiency.
Web technologies are the medium through which enduring engineering principles are explored.
Architecture is one manifestation of understanding. Good UI decisions, thoughtful security trade-offs, sensible engineering trade-offs, empathy for users, and recognising when an AI-generated solution is subtly wrong all stem from understanding — not from any specific technology.
Programming languages, frameworks and AI tools will keep changing. Understanding is what lets you thrive with tomorrow's tools, whatever they turn out to be.
The apprenticeship therefore prioritises understanding over syntax, and systems thinking over tools.
AI is treated as a normal engineering tool, like a compiler or debugger.
AI may:
The engineer remains responsible for:
Emily owns her VM, domain and projects.
She chooses what to build.
Provides intuition, engineering judgement and real-world context through short lectures and mentoring.
Designs missions, adapts the curriculum, reviews work and maintains continuity.
Emily decides what applications she wants to create.
The mentors guide the how, never dictate the what, except for occasional small exercises introducing a new concept.
Ownership drives motivation.
Every project should consider:
Success is when Emily instinctively asks:
"How does this system work?"
and has the confidence to design, build, deploy and improve digital systems independently with AI as a trusted assistant rather than a substitute for engineering judgement.