Overview
Every few years the technology industry announces that everything has changed: the web, the cloud, mobile, and now AI. Each shift produces the same anxiety, and each time, some technologists not only survive but become more valuable. That is not luck. The engineers who endure are running on something deeper than the current toolset: a small set of durable thinking skills that no technology shift can obsolete, because every new technology still has to be understood, evaluated, applied to real problems, and explained to other human beings.
This is a hands-on, foundation course. It builds those skills in a deliberate order: first a clear-eyed look at how technology shifts actually behave, then the fundamentals-first way of understanding any technology, then learning how to learn, then the problem-solving and communication skills that differentiate uncommon engineers, and finally a personal plan for putting it all to work. We deliberately go deep on a few skills that compound over a whole career rather than surveying every professional development topic. Every module ends with a lab, and each module builds on the one before.
Who Should Attend
- Technologists at any career stage who feel the ground moving under them, especially with AI
- Early-career engineers who want to build a durable foundation instead of chasing tools
- Experienced engineers and leads rethinking where their long-term value comes from
Prerequisites
- No specific technical background is required
- Some experience working in or around technology helps the examples land
- A willingness to examine your own habits of learning and thinking
What You Will Learn
- Explain the recurring pattern of technology shifts and why panic is usually a category error
- Judge any new technology by reasoning from fundamentals rather than hype
- Apply a deliberate method for learning a new technology quickly and deeply
- Approach unfamiliar problems with a repeatable first-principles process
- Communicate technical ideas clearly, the single most portable engineering skill
- Build a personal twelve-month plan for becoming more valuable through the current shift
Course Outline
Day one: what survives every shift
- The Pattern of Technology Shifts
- A short history of "this changes everything": what actually changed and what did not
- Why each shift rewards the same underlying skills
- The commodity trap: what happens to engineers whose value is only the current tool
- Lab: map a past technology shift you lived through and identify what stayed valuable across it
- Fundamentals First
- Every abstraction sits on something: reasoning down the stack
- Using fundamentals to see through hype and evaluate new technology honestly
- The current shift as a case study: what AI changes about engineering work and what it cannot
- Lab: take a technology you use daily but do not understand, and reason out how it must work underneath
- Learning How to Learn
- Why uncommon engineers learn faster: mental models over memorized facts
- A deliberate method: survey, fundamentals, build something real, teach it back
- Managing the discomfort of being a beginner again, on purpose
- Lab: apply the method's first two steps to a technology you have been avoiding
Day two: becoming uncommon
- Problem Solving From First Principles
- Separating the actual problem from the assumed solution
- Removing ambiguity: asking the questions everyone else skips
- Working the problem: decomposition, constraints, and checking your reasoning
- Lab: work an unfamiliar, ambiguous problem in pairs using the full process, then compare approaches
- Communication as a Career Multiplier
- Why the engineer who can explain wins: clarity as scarce skill
- Explaining technical ideas to non-technical people without condescension
- Writing and speaking so your ideas travel farther than your commits
- Lab: explain a complex technical concept to a non-technical listener and refine it from their feedback
- Your Plan to Become Uncommon
- Auditing your current value: durable skills versus tool-of-the-day skills
- Choosing what to deepen, what to learn, and what to let go
- A personal twelve-month roadmap, with the first step scheduled
- Lab: write your twelve-month plan and commit to its first thirty days out loud to a partner
Extended Version
The three-day version keeps the same gradient and adds depth and a capstone:
- A deeper treatment of evaluating AI and other emerging technology for your own role and team
- Practice rounds: additional first-principles problem-solving sessions with feedback
- Peer coaching on the personal roadmaps, with revision
- A capstone: each learner presents their plan and one fundamentals-first analysis to the room, keynote style, with structured feedback