PTENES
Skip to content
TRACK 2

🧠 Human Skills

AI has taken over tactical programming—writing code cheaply and well. Your leverage now is moving from tactical to strategic: architecture, vision, delegation, communication, and product control. Your human skills set the ceiling on what AI can deliver.

Illustration: the strategic human mind at the top orchestrating a fleet of tactical AI programmers, in blue and cyan vision delegation communication product STRATEGIC the general at the top AI fleet
6
Modules
36
Topics
~3h
Duration
Inter.
Level
Track progress: 0% 0 of 36

Learning path map

Detailed content

2.1~30 min

♟️ Tactical × Strategic

AI has mastered tactical programming. Your advantage lies in thinking like the general at the top.

What it is:

John Ousterhout distinguishes two ways of programming: tactical and strategic.

Why learn:

It gives you the vocabulary to see where AI is already better than you.

Key concepts:

Two modes; reference book; map of dev work.

What it is:

Day to day: writing code, syntax, finding bugs, creating commits.

Why learn:

It’s exactly the work AI does more cheaply and better.

Key concepts:

Win the battle; execution; syntax and bugs.

What it is:

Think long term: what the codebase should look like and how to work faster.

Why learn:

It’s where your advantage lies — the one AI still can’t replace.

Key concepts:

Win the war; architecture; speed.

What it is:

AI has "eaten" tactical programming—it executes tasks more cheaply and better.

Why learn:

Insisting on competing tactically means swimming against the tide.

Key concepts:

Commoditization of tactical work; an infinite fleet of AI.

What it is:

You need to excel at strategy to get the most out of your tactical AI fleet.

Why learn:

Someone who manages the fleet well is worth far more than someone who only executes.

Key concepts:

Move from tactical to strategic; command the fleet.

What it is:

Spend your time on architecture, speed, and roadmap — not syntax.

Why learn:

It’s the practical application: redirecting your hours toward strategic work.

Key concepts:

General at the top; architecture, speed, roadmap.

View Full
2.2~30 min

📈 Your skills are the ceiling

AI multiplies the impact of people who are already good. Improving yourself means improving AI.

What it is:

"Your skills are the ceiling for what AI can do."

Why learn:

Shows that AI is a multiplier, not a replacement for your expertise.

Key concepts:

Multiplier; the skill's own ceiling.

What it is:

AI makes senior professionals about 10x better at what they already do.

Why learn:

The bigger your foundation, the more AI can unlock.

Key concepts:

Gain proportional to the baseline; senior 10x.

What it is:

Juniors get only a small boost; hiring many of them isn't worth it.

Why learn:

Reframe how you think about teams and where to invest.

Key concepts:

Little benefit at the beginner level; a team strategy.

What it is:

People with low skill can’t get the best out of AI.

Why learn:

Your lack of expertise becomes the ceiling that limits the tool.

Key concepts:

Low ceiling; the human becomes the bottleneck.

What it is:

Getting good with AI = getting good in your domain. A better teacher uses AI to teach better.

Why learn:

Investing in yourself is the highest-leverage investment.

Key concepts:

Domain = leverage; a better teacher with AI.

What it is:

Improving yourself means improving AI—because the multiplier acts on your foundation.

Why learn:

It gives you a direct application: study and practice what actually raises the ceiling.

Key concepts:

Raise the ceiling; multiplier on the base.

View Full
2.3~30 min

🧩 Knowledge × Skill × Wisdom

You can package the first two into skills. Wisdom, you can't.

What it is:

Knowledge is the fundamental understanding you carry in your head.

Why learn:

It’s the foundation, but by itself it doesn’t guarantee you’ll know how to act.

Key concepts:

Understanding; knowing what and why.

What it is:

Skill comes from doing something many times — muscle memory.

Why learn:

Distinguishes “knowing about” from “knowing how to do.”

Key concepts:

Repetition; muscle memory; practice.

What it is:

Wisdom is knowing WHEN to do something and how it fits into the real world.

Why learn:

It’s what separates the competent from the truly good.

Key concepts:

Timing; judgment; fit with reality.

What it is:

Wisdom is almost impossible without living the exact context — to be like someone at Anthropic, you'd need to go to Anthropic.

Why learn:

Explains why you can’t “download” wisdom from outside.

Key concepts:

Lived context; situated wisdom.

What it is:

Knowledge and skill can be packaged into reusable skills.

Why learn:

It’s what lets you distribute expertise to AI and the team.

Key concepts:

Skills package knowledge + ability.

What it is:

Wisdom can't be packaged — it remains your irreplaceable role.

Why learn:

Defines where you need to stay in control, always.

Key concepts:

Delegation limits; wisdom that can't be packaged.

View Full
2.4~30 min

📦 Delegation fundamentals

Delegating to AI is like delegating to a junior developer: scope, interfaces, tests, and documentation.

What it is:

You design the difficult parts up front, before delegating.

Why learn:

The hard decisions are exactly what AI shouldn’t make on its own.

Key concepts:

Difficult decision made early; upfront design.

What it is:

Define the scope of what will be done very carefully before assigning the task.

Why learn:

Vague scope is the #1 cause of incorrect results.

Key concepts:

Clear scope; task limits.

What it is:

Think about the interfaces between modules—the contracts that connect the parts.

Why learn:

Good interfaces let AI work in parallel without breaking everything.

Key concepts:

Contracts; module boundaries.

What it is:

Think through test scenarios and write good tests.

Why learn:

Tests are the safety net that lets AI implement things safely.

Key concepts:

Scenarios; safety net; good tests.

What it is:

Sufficient documentation that points AI to the right places, and a codebase that’s easy to work with.

Why learn:

The right doc reduces back-and-forth and speeds up delivery.

Key concepts:

Directional docs; navigable codebase.

What it is:

The practices are the same as delegating to a junior/mid-level developer.

Why learn:

You already have the mental model; you just need to apply it to AI.

Key concepts:

Classic delegation; management discipline.

View Full
2.5~30 min

🎙️ Communication & dictation

Speaking is overpowered: the speed of getting tokens out of your brain and back in.

What it is:

Being able to put your vision into words, out loud, for the AI.

Why learn:

AI only executes well what you can articulate.

Key concepts:

Articulate the vision; think out loud.

What it is:

The saying is “overpowered”—you put out much more content, much faster.

Why learn:

Speaking is much faster than typing; broadband changes the game.

Key concepts:

Input speed; overpowered dictation.

What it is:

"The speed at which you move tokens out of your brain and back into it."

Why learn:

Seeing the cycle helps you optimize the right bottleneck: communication.

Key concepts:

Brain↔token cycle; bandwidth.

What it is:

Communicating and speaking are ridiculously overpowered in today's dev world.

Why learn:

Communication has become one of the most valuable technical skills.

Key concepts:

Communication as a technical skill.

What it is:

Matt uses Whisper Flow to dictate; dictation tools put this into practice.

Why learn:

The right tool turns speech into real input.

Key concepts:

Whisper Flow; dictation in the workflow.

What it is:

Speaking well is a skill you can train — not a fixed gift.

Why learn:

If it can be trained, it’s worth practicing deliberately.

Key concepts:

Trainable fluency; deliberate practice.

View Full
2.6~30 min

🧭 You’re in control of the product

AI is bad at original ideas. The vision, the why, and the choice of features are yours.

What it is:

AI is notoriously bad at coming up with original ideas.

Why learn:

Shows that the product's originality is still yours.

Key concepts:

AI's limitations; human creativity.

What it is:

"You should be in charge of the product" — you choose the features, have the vision and know the why.

Why learn:

Defines the irreplaceable role of the product owner.

Key concepts:

The product command; the vision and the why.

What it is:

Ask the AI what to REMOVE, how to simplify and improve the UX—not "what's the next big feature."

Why learn:

Use AI where it helps (critique, simplification) and not where it falls short (vision).

Key concepts:

Remove > add; simplify the UX.

What it is:

The fundamentals of product design haven’t changed; the books are still relevant.

Why learn:

You don't need to relearn product thinking—just apply it with AI.

Key concepts:

Durable product fundamentals.

What it is:

Talking to customers, finding out what they need, and building prototypes — that stays the same.

Why learn:

Discovering a real need is human and irreplaceable.

Key concepts:

Customer discovery; prototypes.

What it is:

The fundamentals of business haven’t changed; AI only gives you an execution advantage.

Why learn:

Set the right expectation: AI speeds things up; it doesn’t replace strategy.

Key concepts:

AI handles execution; strategy remains human.

View Full
← Home Track 3: AI Skills (Skills) →