O N T R I A

Hello There!

We're Ontria,
Bringing the future into focus.

Follow Us

Should You Learn
Everything?

There's a quiet pressure in tech
that no one really names. Part 1 of 3.

  • Home
  • Blog
  • Should You Learn Everything in Tech?

Should You Learn Everything in Tech? A Reality Check

Part 1 of 3

There's a quiet pressure in tech that no one really names.

Every few months, a new skill becomes the skill. A new certification trend. A new role appears on LinkedIn that didn't exist last year. And suddenly, what you already know feels… insufficient.

So the question creeps in:

“Should you be learning
different areas of tech?”

Not as a guide. Not as a roadmap. But as an honest question.

The Age of Many Hats

It's no longer strange to see someone with experience in data analysis, product, frontend basics, cloud fundamentals, and a sprinkle of AI.

Multiple resumes. Multiple identities. Multiple "versions" of yourself depending on the role you're applying for.

On the surface, it looks strategic. But underneath, it raises a deeper question:

Is this…

growth or survival?

When Did One Skill Stop Being Enough?

There was a time when being really good at one thing was enough. Now? Job descriptions ask for three roles in one. Entry-level roles want senior experience. Specialists are expected to "understand the bigger picture," while generalists are asked to "go deeper."

So people adapt. They learn adjacent skills. They take courses. They stack certificates. Not always because they're curious — but because standing still feels dangerous.

The Real Cost of Breadth

Here's the uncomfortable truth: More skills don't automatically mean more value.

1

Shallow understanding spread thin — knowing a little about a lot, but not enough to make real decisions in any one area.

2

Constant context switching — never staying long enough in one area to develop judgment or intuition.

3

No real intuition — the difference between someone who's read about PostgreSQL optimization and someone who's debugged a production database at 2am.

Depth

That intuition only comes from staying long enough to understand why things break.

Breadth

But too little of it boxes you in. A backend engineer who's never touched the frontend can't see why their API frustrates everyone downstream.

Maybe the real issue isn't how many skills you have — but why you're collecting them.

Multiple Resumes: Strategy or Identity Crisis?

One for data roles. One for product. One for operations. One for "anything tech-adjacent that pays." Is that smart positioning? Or is it a symptom of uncertainty?

The truth is: it can be both. In unstable markets, flexibility keeps you employed. But here's what multiple resumes actually cost:

You stop trusting
your own story.

Every time you reshape yourself for an algorithm, you're implicitly saying: "Who I actually am isn't enough."

You curate.

You emphasize.

You hide the parts that don't fit.

You forget which version is real.

I've watched people land jobs with Resume Version 3.0, then spend months feeling like an imposter — not because they lack skills, but because they can't remember which narrative they sold.

The real exhaustion

Maintaining the data analyst.

Maintaining the product thinker.

Maintaining the cloud engineer.

Maintaining the AI enthusiast.

Maintaining the "anything that pays" version.

All of them. At once.

Coming Next

Part 2: Are You Learning or Just Performing?

We explore AI anxiety, performative learning, and the difference between boredom and real growth.

Stay tuned
Design development
Design development
Research development
Design Wireframe
High Fidelity Design
Design development