← sources

What 3 Years in Software Engineering Taught Me. Things I’ve learned about writing code, working with people, and growing in tech.

source: reddit (reddit:developersIndia)published 2026-09-26 15:25ingested 2026-09-27 02:36

retained text

Three years ago, when I started working as a software engineer, I had a pretty simple idea of what being good at this job meant.  
Write good code. Know your DSA. Learn new technologies. Don’t break production.  
Three years later, working as a Senior Software Engineer at a product based company in Bangalore, I think I had only understood a small part of it.  
A lot of what I’ve learned has had very little to do with syntax or frameworks.  
You’re never going to know everything  
This was probably the first thing I had to accept.  
There have been so many times when I’ve been in a discussion and someone mentioned something I had absolutely no idea about.  
Initially, that bothered me. You start wondering whether everyone around you knows more than you do.  
Eventually, you realise everyone has gaps.  
Even experienced engineers Google basic things. People ask questions. People misunderstand requirements. People spend hours debugging something only to discover that the problem was embarrassingly simple.  
You don’t need to know everything.  
You need to be comfortable saying, I don’t know, let me check.  
Writing code is sometimes the easy part  
This surprised me.  
You can spend hours discussing something that eventually becomes 20 lines of code.  
What exactly are we trying to solve? What happens if this service goes down? Do we really need to build this? Will this solution still work if traffic increases? Are we making something unnecessarily complicated?  
The more experience I’ve gained, the more time I’ve found myself spending on questions like these.  
Sometimes the best contribution you can make isn’t writing more code. It’s stopping the team from writing code that doesn’t need to exist.  
Production will humble you  
Everything looks great until real users start using it.  
You test something locally. It works.  
It passes code review.  
It works in staging.  
You deploy it.  
And somehow production finds a scenario nobody thought about.  
Those experiences can be stressful, but they teach you a lot. You become more careful about logging, monitoring, edge cases and what happens when things fail.  
You also learn not to panic every time something goes wrong.  
Find the problem. Limit the impact. Fix it. Understand why it happened. Move on.  
Communication matters way more than I expected  
As a fresher, I thought technical skills would carry most of my career.  
They definitely matter, but being able to communicate clearly makes a huge difference.  
Can you explain why you chose a particular approach?  
Can you disagree with another engineer without turning it into an ego battle?  
Can you tell your manager early that something is going to take longer instead of waiting until the deadline?  
Can you explain a technical problem to someone who isn’t an engineer?  
These things don’t show up in coding interviews very often, but you deal with them constantly at work.  
Being senior doesn’t mean having all the answers  
This is something I understand much better now.  
I used to associate seniority with knowing more.  
And yes, experience and technical depth matter.  
But I think a big part of it is ownership.  
When something is unclear, do you try to bring clarity?  
When a teammate is stuck, can you help them without simply doing the work for them?  
When something goes wrong, are you looking for someone to blame or trying to understand what failed?  
And when you don’t know something, are you comfortable admitting it?  
I still ask plenty of questions. I still get things wrong. I still come across technologies I know almost nothing about.  
The difference is that I’m much more comfortable with that now.  
Comparison never really ends  
Tech makes comparison ridiculously easy.  
Someone your age is already a Staff Engineer.  
Someone just switched companies with a massive hike.  
Someone is working at a company you’ve always wanted to join.  
Someone on LinkedIn apparently wakes up at 5 AM, solves three LeetCode problems, contributes to open source, reads a system design book and somehow still has time for the gym.  
There will always be someone ahead of you on some metric.  
I’ve slowly stopped treating every LinkedIn update as evidence that I’m falling behind.  
I’m trying to focus more on whether I’m better than I was a year ago.  
That’s been much healthier.  
Three years isn’t that long  
Maybe that’s the biggest thing I’ve realised while writing this.  
Three years felt like a huge amount of experience when I was in college.  
Now it feels like I’ve only started understanding how much there is to learn.  
There are still systems I don’t understand, mistakes I haven’t made yet and probably a lot of opinions I have today that I’ll disagree with five years from now.  
And I’m okay with that.  
I’m starting this Substack mostly to write about software engineering, career growth, product companies, things I learn at work, and occasionally life in Bangalore.  
I don’t know exactly what this newsletter will turn into yet.  
But I figured the best way to find out was to start writing.  
So, here we are.

document fetched 2026-09-27 00:25 · canonical https://reddit.com/r/developersIndia/comments/1wqta70/what_3_years_in_software_engineering_taught_me