The new tools of the trade
You are here because you can just do things. You were selected because you’re agentic, a self-starter, and have the core traits needed in today’s AI-empowered world: systematic thinking, strong communication skills, and a bias toward making messy things legible
Here are the new tools of the trade
The way we work has fundamentally changed. AI means that structured problem-solvers — the people trained to break down ambiguous problems, communicate clearly, and orchestrate complex workstreams — can now build production software. The technical bar has dropped. The thinking bar hasn't. You already have what it takes
This archetype — agentic, systematic, communication-first — has real potential to outperform traditional software engineers in the AI era. A pure technician can write code. You can hold the whole problem in your head. The ability to decompose ambiguity, manage stakeholders, and context-switch across domains is exactly what modern AI-assisted engineering rewards. When the bottleneck shifts from typing code to knowing what to build and why, the consultant-turned-engineer has a real edge
“Generalists who straddle disciplines — business, design, infrastructure, and user needs all at once.”
Boris Cherny, Head of Claude Code — on the profile of the new builder
Vibe coding creates maintenance debt faster than it creates value. Everyone can code now, but that doesn't mean everyone knows how to build. The difference is understanding the layers underneath — what makes something shippable, maintainable, and real
Two modules. The minimum you need to go from “I've never deployed anything” to shipping a working application into production
The ten layers of shipping something real. Environments, version control, databases, hosting, domains, auth, scheduled jobs, workers, scale, and system design — each explained as a standalone concept with the context you need to understand why it matters
What reusable modules look like and why you should build them. Examples of packaging common patterns — notifications, data feeds, scraping — so every future project starts from a higher baseline
Start with Level Up. That’s the foundation — the layers every production app needs regardless of what you’re building. The Stack shows you what to build on top once you have the fundamentals
Think of this like a consulting deck. The framing page is what you need to ship. The deep dives are each layer unpacked
| Layer | What it does | Options |
|---|---|---|
| Application | The code that solves a problem | Python, React, Flask |
| Version Control | Track changes, collaborate, undo mistakes | Git, GitHub |
| Database | Persist data between sessions | Supabase, Postgres, SQLite |
| Search | Find things in large datasets | TF-IDF, cosine similarity, pgvector |
| Hosting | Run your code on the internet | Vercel, Dokku, Railway |
| Routing | Domain, DNS, SSL | Cloudflare, Squarespace DNS |
| Auth | Control who accesses what | OAuth, JWT, session cookies |
| Scheduled Jobs | Run code when nobody is watching | Cron, Celery Beat, GitHub Actions |
| Workers & Scale | Move slow work out of the request path | Celery, RQ, nginx, HAProxy |
| System Design | Structure ambiguous technical problems | Requirements, trade-offs, MVP vs. scale |
Each of these is a chapter in Level Up. Master them and you can ship anything
You don’t need to master everything before you start building. You need to understand the layers, then go find yourself a problem to solve. Every engagement sharpens the next one
Once you have the foundation, you start building reusable modules — The Stack shows what that looks like. Notifications, data feeds, scraping, inference — each one packaged so it can be imported into any future project with one line
The structured problem-solving, communication, and orchestration that made you a good consultant will make you the ideal forward deployed engineer