😨 What will happen to the dev in me?
March 21, 2026 · 2 min read
When I school, I wanted to become a scientist. But my work ethic(read laziness), talent and my parent's pocket suggested I should be an engineer instead. Trusting the data, I became one.
I liked computers. It is a product of Scientific progress, and it is a fascinating machine indeed. I learnt to code, forgot because my first job didn't require it, re-learned and since then I was doing OK till 2025.
But now Codex and Claude writes way better code, and me, who never worked hard to look at the bigger picture seriously when developing features in a big-ass enterprise application, now feels replaced, kinda. My work has now boiled down to writing comprehensible English and provide adequate context to the agent so that it can figure out what is to be done.
So now I have no choice but to become THE ARCHITECT. The architect, who knows every piece of tech that is used to build a software. Not in deep, but enough to know what to ask the agent to do. People need T shaped knowledge.
Good at one, okay at all.
I'm preparing myself to go down the tutorial rabbit hole again, this time with a little bit of building stuff sprayed in. Let's see how this goes.
function knowItAll() {
return Promise.all([frontend(), backend(), agenticWorkflow(), devops()]);
}
async function frontend() {
await learn("react");
}
async function backend() {
await learn("nodejs");
}
async function agenticWorkflow() {
await learn([
"prompt engineering",
"context engineering",
"agent orchestration",
"agent skills",
"tool calling",
]);
}
async function devops() {
await learn(["kubernetes", "docker", "terraform", "CI/CD"]);
}