Don't lock in your skills

I have been thinking a lot about how we learn in tech.

Not only what we learn, but how we learn it.

Today, it is very easy to learn React, Angular, Tailwind, Next.js, or any other framework by following tutorials, bootcamps, and copy-paste examples.

And to be clear, this is not a post against frameworks.

I use frameworks. I like them. They help us move faster.

But there is a problem when we learn only the tool and skip the fundamentals behind it.

Because then we are not really learning software development.

We are learning how to operate one abstraction.

And abstractions change.

The shortcut feels productive

Many people want to take the shortest path.

Learn React. Learn Tailwind. Learn a component library.

Build a portfolio. Get a job.

And honestly, I understand it.

The industry also rewards this from the outside. Job descriptions mention tools. Bootcamps sell tools. Tutorials are usually framework-first because it is easier to show results quickly.

You can build something visible in a few hours.

That feels good.

But sometimes this creates a dangerous illusion: we think we understand why things work, when actually we only know the steps to make them work.

For example, someone can build a React app without understanding the browser deeply.

They can use Tailwind without understanding CSS fundamentals.

They can use Next.js without understanding rendering, caching, HTTP, or how the web works.

At the beginning, this may not feel like a problem.

Until something breaks. Until performance is bad. Until the framework changes.

Until AI starts generating the same code that you learned by memory.

Cognitive load is being used in the wrong place

Learning a new framework already takes mental energy.

You need to remember syntax, folder structures, conventions, libraries, patterns, and “the right way” to do things.

That is cognitive load.

The problem is when all that mental energy goes into memorizing abstractions, instead of understanding the principles behind them.

We spend time asking: “How do I do this in React?”

But we spend less time asking:

“Why is this needed?”

“What problem is this abstraction solving?”

“What happens under the hood?”

“Would I understand this problem without the framework?”

This is where I think many developers get trapped.

They become fast inside one ecosystem, but fragile outside of it.

That is also a form of vendor lock-in. Not in your infrastructure. In your skills.

Specialization is not the enemy

I do not think everyone needs to be a low-level expert.

I also do not think we should reject specialization.

Specialization is valuable.

A strong React developer, Angular developer, backend engineer, DevOps engineer, or product-minded engineer can create a lot of value.

But specialization becomes risky when it is not built on fundamentals.

Because then your value depends too much on one tool staying relevant.

And tech does not work like that.

Tools change. Frameworks change. Trends change. The market changes.

Now, with AI, this is becoming even more obvious.

If your main skill is remembering how to write boilerplate code, AI will probably do that faster than you.

But if you understand the fundamentals, AI becomes a tool that helps you move faster.

You can review its output. You can challenge it. You can adapt it.

You can use it to learn new things instead of feeling replaced by it.

Fundamentals help you reinvent yourself

The people who invest time in fundamentals usually look slower at the beginning.

They ask more questions. They go deeper.

They spend time understanding the browser, HTTP, accessibility, state, data flow, architecture, testing, performance, and product trade-offs.

From the outside, it may look like they are not moving as fast as the person following shortcuts.

But in the long run, they are building something stronger. They are learning how to think.

And when the industry changes, they can move again.

Maybe from Angular to React.

Maybe from React to server components.

Maybe from frontend to full-stack.

Maybe from coding everything manually to working with AI tools.

The framework may change, but the thinking stays.

Learning for the long run

I believe we need to be careful with how we learn.

It is fine to learn React. It is fine to learn Tailwind. It is fine to learn any framework that helps you build.

But do not stop there.

Ask what problem the tool is solving.

Ask what existed before it.

Ask what trade-offs it introduces.

Ask what you would do if the tool disappeared tomorrow.

Because the goal is not to become loyal to a framework. The goal is to become adaptable.

And adaptability comes from fundamentals. Not from memorizing the current abstraction.

Final thought

Shortcuts can help you start. But fundamentals help you stay.

In a world where tools change faster than ever, the best investment is not only learning the next framework.

It is learning how to think beyond it.