@mattpocockuk: Tactical vs Strategic Programming, and why I'm nervous for juniors: Good programming involves a mix of tactical and str…
Summary
Matt Pocock discusses how AI agents have absorbed tactical programming tasks, shifting developer work to purely strategic thinking, and raises concerns about how to train junior developers when entry-level tactical work disappears.
View Cached Full Text
Cached at: 05/21/26, 08:14 AM
Tactical vs Strategic Programming, and why I’m nervous for juniors:
Good programming involves a mix of tactical and strategic decision-making:
- Tactical: on the ground, short-term. The soldier doing the fighting.
- Strategic: high-view, long-term. The general planning the war.
You need to be a tactician to write good code. To choose the right syntax. To figure out the file structure. To figure out how best to test your changes.
But you need to be a strategist to build code that lasts. To design the architecture. To automate away problems. To think beyond today.
Agents have eaten the tactical part of programming. When you can pay below minimum wage for code, there’s no point going into the trenches yourself.
But AI cannot code strategically. Agents need someone at the top of the pyramid to tell them what to do. They need oversight.
So, a developer’s day-to-day job has become 100% strategy. Long-term thinking, all the time. (maybe this is why I’m so tired all the time now)
If you identify as a tactical programmer - a code monkey - then you are out of luck. The job has changed.
Personally, I like it. I always preferred thinking strategically about code. If you asked me what my job was about, I’d say ‘building apps’, not ‘writing code’.
But what makes me nervous is that we’ve pulled down the only bridge that brought juniors into the industry.
We used to train juniors like this:
- Give them only tactical tasks
- Let them build up their strategic experience slowly
Eventually, they are a good enough strategist that they are no longer a junior.
But what happens when all tactical code is written by AI? What is the point of a junior?
We obviously need juniors. We need new lifeblood coming into the industry. We need to leave paths open for extraordinary hires to enrich our companies.
But how do we train them? How do you train strategic thinking?
These are the questions I’m thinking about. I’d love to know your thoughts.
Similar Articles
@mattpocockuk: Steps to become a senior programmer: 1. Install my /teach skill npx skills add mattpocock/skills --skill teach 2. Creat…
Matt Pocock shares steps to become a senior programmer using his /teach skill and a coding agent like Claude, focusing on strategic programming skills.
@AskYoshik: I am begging juniors to pivot into DevOps / SRE. Systems knowledge is more important than it's ever been. AI can write …
A tech commentator advises junior developers to pivot into DevOps/SRE, arguing that systems knowledge is increasingly critical because AI can write code but cannot manage production systems.
@0xDepressionn: Karpathy: "I've never felt this much behind as a programmer. And I've been doing this for 20 years." I've watched hundr…
Andrej Karpathy shares insights on the rapid shift to AI-assisted programming, predicting 2025-2035 as the 'decade of agents' and describing his personal transition from 80% manual to 80% AI coding in just 30 days.
@rohit4verse: AI didn't make code cheap. it made bad code lethal. Matt Pocock: "Software fundamentals matter more than ever" AI in a …
Discusses how AI amplifies code quality, emphasizing that software fundamentals matter more than ever, and recommends five design patterns for building reliable AI agents.
@mattpocockuk: This video has 96K hours of watch time That's over a decade Still have to pinch myself sometimes
Matt Pocock argues that effective AI-assisted development requires respecting LLM limitations, specifically the 'intelligence zone' and amnesiac context windows, advocating for small tasks and clear system prompts over vague specifications.