Am I really in tech or not?
Honestly, there’s no “in between” in tech. You are either building, learning, or you are just… watching from the sidelines.
A lot of people quietly struggle with this question. What actually qualifies someone as a developer? Do I need 10 languages? A big job title? A fancy GitHub?
Let’s clear that up.
To be in tech simply means you are specialized in a direction and actively building within it. Even systems that look like they “know everything” are still built on deep specialization under the hood.
Now the real confusion usually starts here:
“Is Python enough to call myself a developer?”
“Do I need TypeScript, Go, Rust, Java, and maybe one alien language?”
The honest answer is yes… Python is enough. TypeScript is enough. But not in the way most people think.
And this is where people start entering what I call the “language hopping loop” 😄
You learn Python.
You build a few projects.
Then someone says “JavaScript is where the jobs are.”
You switch.
Then another person says “Go is better for scalability.”
You switch again.
At that point, you are not learning deeper systems anymore, you are basically doing load balancing… but for your attention span 😭
And the result?
You might even land interviews, but when they ask deeper questions like system design, caching strategies, or how your API handles concurrency, things start feeling… blurry.
Because the issue was never the language.
There is no “best language”. There is only context.
Python is not better than TypeScript. TypeScript is not better than Python. They are just tools optimized for different workloads, like how caching, indexing, and database choice depend on the system you are building.
So how do you actually get into tech properly?
Not the usual “learn a language, build a todo app, become senior engineer in 2 weeks” story 😄
The real path is deeper than that.
Start with a language. Yes.
But don’t stay at surface level.
Go beyond syntax:
- understand how memory is managed
- learn how APIs actually handle requests under the hood
- explore scalability concepts like load balancing and caching
- break things, fix them, rebuild them better
Think of it like mathematics.
You don’t stop at BODMAS and call it a day. You move into algebra, calculus, and eventually deeper problem solving where everything connects.
Tech is the same.
Once you pick a path, start building real things. Then revisit them as your knowledge grows. Improve the architecture. Refactor the design. Optimize performance. That is where growth actually happens.
And over time, something interesting happens.
You stop saying “I know Python” and start saying “I understand systems.”
That shift is what I like to call the transition from learning mode to improvement mode.
It’s a bit like solo leveling 😄
And here’s the final truth:
Once you deeply understand one stack, moving to another becomes easier. Not because it is similar, but because your thinking has already adapted to complexity.
That’s when you are truly in tech.
Not because you know everything, but because you know how to learn anything.
Every week, I will be sharing more of these, focused on practical technical growth, deeper understanding of systems, and lessons that actually help you become a better builder in tech.
If you’re on the same journey, stick around. There’s more coming!!!
