How to start thinking like an engineer or developer

Harsh Sharma — Thu, 05 Feb 2026 12:43:59 +0000

When people say “think like an engineer”, most beginners assume it means knowing more languages, frameworks, or complex math.

But honestly, thinking like an engineer starts way before all that.

It starts with learning how to face problems.

And by facing problems, I don’t mean solving LeetCode questions all day.

I mean understanding what the real problem actually is.

You can’t solve a problem you don’t understand

No one can truly face a problem until they clearly know what the problem is.

For example, a normal user might use a UI library and feel it’s “nice.”

But a frontend developer understands the pain points:

repetitive components
inconsistent styles
slow development
bad developer experience (DX)

That’s why tools like shadcn/ui exist.

Not because someone randomly wanted to build a UI library, but because someone felt the pain of building the same things again and again.

Same with Postman.

A non-developer doesn’t care how APIs are tested.

But backend and frontend developers feel the pain of debugging:

requests
headers
tokens
responses
errors

Postman was born because someone deeply understood that problem.

Problems don’t appear magically.

They are experienced.

Try things, break things, feel the pain

If you want to become a better engineer, you must try different things.

Build projects
Try tools
Fail
Get stuck
Google weird errors at 2 AM

Because only when you struggle do you start asking better questions:

Why is this slow?
Why is this hard to maintain?
Why does this break so easily?
Why does this feel repetitive?

These questions are the real beginning of the engineering mindset.

An engineer is not someone who knows everything.

An engineer is someone who has felt enough problems to recognize patterns.

Understanding the flow changes everything

Once you start building real projects, you slowly begin to understand the flow of things.

How data moves
How systems talk to each other
How one small decision affects many parts of the system

And when you understand the flow, something interesting happens.

You start seeing loop holes.

You notice:

unnecessary steps
repeated logic
bad abstractions
fragile parts of the system

This is where thinking like an engineer truly starts.

Not at the keyboard.

Not in tutorials.

But in your head.

Final thought

Thinking like an engineer is not about being smart.

It’s about being:

curious enough to face problems
patient enough to understand them
brave enough to experiment

So:

Build more.

Break more.

Feel the pain.

That’s how engineers are made.

[Boost]