This blog post assumes the following hypothesis is true: AI agents are going to write all code in the future,
Assuming writing code is becoming less valuable, coding can’t be the only tool in your toolbox. So what should you fill it with instead?
Should we all become duck farmers instead?
Be a builder
If someone else is doing the typing we need to start focusing on the outcomes instead. Engineering is still going to be needed, but we have to change our focus. Focus on what the code achieves on a bigger level. The what, instead of the how. We need to build an understanding of the problems to be solved, and communicate the solutions to humans and AI agents alike.
Tools to unlock: Design thinking, systems thinking, architecture, diagramming, technical writing, presentation technique
Be a planner
I don’t mean literally be a project manager, but be the person on your team that makes sure things happen. Many developers like coding and making the perfect little thing. Be the person who makes sure your team delivers value with each iteration. Do this by syncing with stakeholders and helping your team break things down into managable deliverables. Communicate this with the stakeholders to manage expectations.
Tools to unlock: Planning, estimation techniques, presentation technique, stakeholder management
Be a debugger
Bugs exist in the gaps between what the code does and what you need it to do. Finding these gaps is a human skill that is going to be hard to replace. To be able to do this you need experience reading and debugging code, and a soid understanding of the strengths and weaknesses of your technology stack. Learn how to use tracing tools and local debuggers. Learn how to communicate with others to learn how the system should function.
Tools to unlock: Systems thinking, building a mental model of the code base, diagramming
Be a reviewer
Code being easier to produce is going to make reviewing code a bottleneck. Identify what to focus on in a review, and navigate code changes quickly is already a core competency, but will become more so Post-AI. Learn how to navigate your git repository and code base quickly. Maybe look into git worktrees to make switching branches frequently more ergonomic.
Tools to unlock: Advanced Git, navigating a large code base, diffing
Conclusion
I don’t believe we will stop writing code, I honestly think its laughable to suggest it. However I think we have to change how we communicate and think about what we do. The role code monkey is dead, I’m not particularly sad or worried about that. Unlocking the tools I outlined in this post is going to be useful no matter how the AI-bubble shakes out.