Best advice on how to transition from junior dev to a senior dev

Oct 22, 2025 · 3:04 AM UTC

45
653
44
6,822
0
Replying to @AbhinavXJ
this guy is smart
6
177
🔥🔥🔥
3
Replying to @AbhinavXJ
Smort
1
4
Replying to @AbhinavXJ
stop writing code to make it work. start writing code so others can.
Replying to @AbhinavXJ
Agree, have this feeling when I rebuild something I made a year ago. You analyze your code and see where you got better.
2
17
Replying to @AbhinavXJ
Reinventing the wheel in the service of learning is always a worthwhile endeavor. Sometimes it actually ends well in a production environment as well but, only if you're already a senior developer with serious, serious chops.
12
Replying to @AbhinavXJ
exactly building my own redis from scratch
Kunal @Kashy53717Kunal
Oct 22
>configured listening port for data replication from master to slave and wrote resp protocol for same >Added more support for decoupling and allowing user to queue commands like Kafka >Learnt about RDB persitance in DB
11
Replying to @AbhinavXJ
Reading almost 1K lines of SQL code made me from Junior to Mid.
1
6
Replying to @AbhinavXJ
It's always amazed me how people don't already do this. Like how do you expect to learn and grow?
6
Replying to @AbhinavXJ
For a start people should try to avoid python requests in the beginning and rather use urllib when they need to write http clients or APIs.
3
Replying to @AbhinavXJ
I agree! I built a key value datastore last month in C and it's actually faster than redis. Uses a single-threaded, non-blocking event loop with I/O multiplexing using epoll on linux and kqueue on macOS. Learned a lot about C and systems like Redis. github.com/AlexJuca/fkvs

GitHub - AlexJuca/fkvs: fkvs is a in-memory, NoSQL key-value data structure store and database...

fkvs is a in-memory, NoSQL key-value data structure store and database written in C - AlexJuca/fkvs

github.com
2
Replying to @AbhinavXJ
The best way is just write senior on your resume Instant upgrade
1
Replying to @AbhinavXJ
What I cannot create, I do not understand
1
Replying to @AbhinavXJ
Thanks Abhinav, this is great advice
1
Replying to @AbhinavXJ
This is what I've been doing. But feel like I'm getting no where
1
Replying to @AbhinavXJ
great advice absolutely do not do this on the job and don't ever suggest rebuilding non-trivial existing functionality until you're a sr
1
1
Replying to @AbhinavXJ
So wise.
1
GIF
Replying to @AbhinavXJ
Best advice ever
Replying to @AbhinavXJ
I recommend going through step-by-step YT tutorials building some mainstream apps to learn about patterns and anti-patterns too
Replying to @AbhinavXJ
Wait, a transition?
Replying to @AbhinavXJ
This is the best thing I’ve heard today.
Replying to @AbhinavXJ
🫡
Replying to @AbhinavXJ
Yes
Replying to @AbhinavXJ
1 of the few tech influencers I appreciate
Replying to @AbhinavXJ
On point
Replying to @AbhinavXJ
Great advice. Will try to work over it.
Replying to @AbhinavXJ
@grok bu adam tam olaraq ne deyir ? Tercume etsen sevinerem
1
Replying to @AbhinavXJ
love this guy.
Replying to @AbhinavXJ
Solid advice
Replying to @AbhinavXJ
1000%
Replying to @AbhinavXJ
Spot on
Replying to @AbhinavXJ
@grok who is this?
2
Replying to @AbhinavXJ
I learnt so much from thePrimeAgen
Replying to @AbhinavXJ
Def gonna copy some projects
Replying to @AbhinavXJ
Lead your employer???. Definitely not my employer 😄
Replying to @AbhinavXJ
This is what I do, when I work on projects,encounter a problem, I discuss it with ai to come up with a solution in code, which I also understand, not simple copy paste , should I do this or should I do stuff on my own,finding my own solution & architecture,not following practices
Load more