After four years of Computer Science engineering, a startup experience, and now working at an MNC, I thought I'd have most things figured out.
I believed that by this point, I'd feel confident about my technical knowledge and have a clear understanding of the software industry.
But the deeper I went into tech, the more I realized how much I still didn't know.
Not in a discouraging way.
Just in a humbling way.
The Reality Check
Like many Computer Science students, I spent years learning data structures, algorithms, databases, operating systems, networking, software engineering, and programming languages.
I built projects.
I fixed bugs.
I participated in hackathons.
I learned frameworks and tools.
And eventually, I got the opportunity to work in both a startup and later an MNC.
Naturally, I felt like I had a decent understanding of software development.
Then I started exploring beyond my day-to-day work.
That's when I began coming across topics like:
- System Design
- Cloud Architecture
- Distributed Systems
- Linux Internals
- Cybersecurity
- Cryptography
- AI/ML
- MLOps
- Networking at Scale
- Open Source Ecosystems
And what surprised me wasn't how difficult these topics were.
It was realizing how many more topics existed beyond them.
Every rabbit hole seemed to open three more.
When Imposter Syndrome Creeps In
I remember reading posts from experienced engineers discussing concepts I had never heard of before.
Large-scale architectures.
Observability.
AI infrastructure.
Performance engineering.
Security.
Sometimes I'd find myself scrolling through discussions thinking:
"Wait... people actually understand all of this?"
That's usually when imposter syndrome would show up.
Questions like:
"Am I behind?"
"Should I already know this?"
"How does everyone else seem so knowledgeable?"
started creeping into my mind.
The more I explored, the bigger the gap felt.
What Changed My Perspective
Over time, I started paying closer attention to the engineers I looked up to.
Senior engineers.
Staff engineers.
Architects.
People with years of experience.
And I noticed something interesting.
They weren't pretending to know everything.
- Many of them openly talked about what they were currently learning.
- Some were learning AI.
- Others were diving deeper into cloud infrastructure.
- Some were exploring security.
- Others were trying to better understand distributed systems.
The common pattern wasn't expertise.
It was curiosity.
That's when something clicked for me.
- Maybe being a good engineer isn't about knowing everything.
- Maybe it's about staying curious enough to keep learning.
My "Things I Don't Know Yet" List
One habit that has helped me a lot is maintaining a simple note called:
"Things I Don't Know Yet."
Whenever I come across a topic I don't fully understand, I add it to the list.
Not because I need to learn everything immediately.
But because I don't want to forget it.
Today, that list contains things like:
- Advanced System Design
- Cloud Architecture at Scale
- AI/ML beyond tutorials
- MLOps and AI Deployment
- Cybersecurity
- Linux Kernel Internals
- Distributed Systems
- Networking
- Cryptography
- Open Source at Scale
Some items stay there for months.
Some get checked off.
And somehow, new ones keep getting added.
Earlier, that would've bothered me.
Now I see it differently.
The growing list isn't proof that I'm falling behind.
It's proof that I'm still discovering new things.
Why This Small Habit Helps
The biggest benefit isn't that it makes me learn faster.
It's that it reduces the pressure.
Instead of feeling overwhelmed by everything I don't know, I simply write it down.
The list becomes a roadmap instead of a reminder of my limitations.
Every few months, I revisit it.
Some topics that once looked intimidating suddenly make sense.
Some are still waiting their turn.
And new topics appear that I didn't even know existed before.
That's become one of my favorite parts of working in tech.
There's always another layer to uncover.
The Rabbit Hole Never Ends
One thing I've learned is that software engineering is much broader than it appears from the outside.
You learn web development.
Then you discover system design.
System design leads you to distributed systems.
Distributed systems lead you to networking, infrastructure, and observability.
AI introduces entirely new worlds.
And every path branches into several more.
The deeper you go, the more you realize there isn't a finish line.
And honestly, that's okay.
Because that's also what makes this field exciting.
What I Tell Myself Now
These days, whenever I encounter something unfamiliar, I try not to think:
"I should already know this."
Instead, I remind myself:
"I don't know this yet."
That one word changes everything.
It turns a knowledge gap into a future learning opportunity.
And it reminds me that growth isn't about having all the answers.
It's about being willing to find them.
Final Thoughts
If you're a student, fresher, or early-career developer feeling overwhelmed by how much there is to learn, you're not alone.
I've felt that way.
I still do sometimes.
But I've learned that the best engineers aren't the ones who know everything.
They're the ones who keep learning.
So now, whenever I discover something I don't understand, I don't see it as a weakness.
I add it to my "Things I Don't Know Yet" list.
And then I move forward.
One step at a time.
That's how engineers grow.
Top comments (0)