Who Are You Becoming?
The final part of the series.
Part 3 of 3.
Who Are You Becoming?
So. What's the point of learning multiple areas?
The answer isn't specialisation or generalisation.
Maybe it's:
Depth in one core area: the thing you can defend in a technical argument
Breadth that supports it: enough context to collaborate and see problems clearly
A story that connects the dots: not “I can do everything,” but “here's how what I know fits together”
Coherence, Not Collection
A data analyst who learns SQL deeply, picks up enough Python to automate repetitive work, understands how dashboards influence decisions, and can explain why their analysis matters to the business. That's coherence.
They're not trying to become a full-stack data scientist. They're building leverage around what they already do well.
The Question That Actually Matters
Before your next course, certification, or pivot, ask:
The Filter
Am I learning this to escape uncertainty, or to build leverage?
Does this skill compound with what I already know?
Will I apply this, or just post about it?
Can I explain why this matters to my work in two sentences?
Because the goal isn't to outrun AI.
It's to develop judgment, context, and problem-solving. The things that don't get automated easily.
A junior developer who's memorised 50 JavaScript methods is less valuable than one who can debug a gnarly production issue by reasoning about how systems fail.
Who Are You Becoming?
Maybe the question was never:
“Should I learn more?”
“Who am I becoming through
what I'm choosing to learn?”
Because here's what no one tells you:
Every time you choose breadth over depth, you're choosing optionality over mastery.
Every time you chase the next trend, you're choosing safety over conviction.
Every time you learn for the resume instead of the work, you're choosing performance over transformation.
None of these choices are wrong. But they compound.
At some point, you'll look up and realise: you've built a career of surfaces.
Impressive on LinkedIn. Uncertain in the room.
You've built something coherent. Something that reflects actual choices, not just reactions to fear. You can explain what you know and why it matters. You can solve problems, not just cite frameworks. You trust your own story.
That version of you? That's not someone AI can replace.
Not because you know more tools. But because you've learnt how to think.
And thinking. Real, hard-won, context-aware thinking. It's still the rarest skill in tech.
So learn what you want.
Just know why.
Series Complete
Should You Learn Everything in Tech?
This was the final part of the three-part series.
Read from the beginning ●