DEV Community

Gautam wise
Gautam wise

Posted on

๐—ง๐—ต๐—ถ๐—ป๐—ด๐˜€ ๐—œ ๐˜„๐—ถ๐˜€๐—ต ๐—œ ๐—ธ๐—ป๐—ฒ๐˜„ ๐—ฏ๐—ฒ๐—ณ๐—ผ๐—ฟ๐—ฒ ๐—ฏ๐—ฒ๐—ฐ๐—ผ๐—บ๐—ถ๐—ป๐—ด ๐—ฎ ๐—ฆ๐—ฒ๐—ป๐—ถ๐—ผ๐—ฟ ๐——๐—ฒ๐˜ƒ๐—ฒ๐—น๐—ผ๐—ฝ๐—ฒ๐—ฟ ๐Ÿ‘จโ€๐Ÿ’ป

When I started coding, I honestly thought being a good developer meant:

โšก Writing code quickly
๐Ÿง  Knowing every new framework
๐Ÿ”ฅ Fixing bugs at 2 AM
๐Ÿ“š Learning every new technology
๐Ÿ’ป And probably having 100+ tabs open ๐Ÿ˜‚

But after working on real projects for a few yearsโ€ฆ

I realised itโ€™s actually very different.

You start dealing with production issues, deployments, servers going down, unexpected bugs, database problems, and that one bug that somehow works perfectly on your machine. ๐Ÿ˜…

And slowly, you start learning things that aren't really taught in tutorials.

1๏ธโƒฃ Y๐—ผ๐˜‚ ๐—ฑ๐—ผ๐—ป'๐˜ ๐—ฎ๐—น๐˜„๐—ฎ๐˜†๐˜€ ๐—ป๐—ฒ๐—ฒ๐—ฑ ๐˜๐—ผ ๐˜„๐—ฟ๐—ถ๐˜๐—ฒ ๐—บ๐—ผ๐—ฟ๐—ฒ ๐—ฐ๐—ผ๐—ฑ๐—ฒ.

Earlier, my first thought was:

โ€œLet's build something for this.โ€

Now it's more like:

โ€œDo we actually need to build this?โ€

Sometimes a simple solution is better than creating a huge architecture for a small problem.

2๏ธโƒฃ ๐——๐—ฒ๐—ฏ๐˜‚๐—ด๐—ด๐—ถ๐—ป๐—ด ๐˜๐—ฒ๐—ฎ๐—ฐ๐—ต๐—ฒ๐˜€ ๐˜†๐—ผ๐˜‚ ๐—ฎ ๐—น๐—ผ๐˜.

Anyone can write code when everything is going well.

The real learning starts when something breaks.

Check the logs.
Reproduce the issue.
Understand what is actually happening.
Then fix it.

And yesโ€ฆ

Sometimes you still restart the server first. ๐Ÿ˜‚

3๏ธโƒฃ ๐—ฃ๐—ฟ๐—ผ๐—ฑ๐˜‚๐—ฐ๐˜๐—ถ๐—ผ๐—ป ๐—ถ๐˜€ ๐—ฎ ๐—ฑ๐—ถ๐—ณ๐—ณ๐—ฒ๐—ฟ๐—ฒ๐—ป๐˜ ๐˜๐—ฒ๐—ฎ๐—ฐ๐—ต๐—ฒ๐—ฟ.

Everything looks easy in development.

Then you deploy it.

And suddenly:

โ€œWhy is the server using 98% CPU?โ€ ๐Ÿ˜

โ€œWhy is this API taking 10 seconds?โ€

โ€œWhy did this work yesterday?โ€

These problems can be frustratingโ€ฆ

but honestly, they teach you more than many hours of watching tutorials.

4๏ธโƒฃ ๐——๐—ผ๐—ป'๐˜ ๐˜๐—ฟ๐˜† ๐˜๐—ผ ๐—น๐—ฒ๐—ฎ๐—ฟ๐—ป ๐—ฒ๐˜ƒ๐—ฒ๐—ฟ๐˜† ๐—ณ๐—ฟ๐—ฎ๐—บ๐—ฒ๐˜„๐—ผ๐—ฟ๐—ธ.

React โ†’ Next.js โ†’ New framework โ†’ New AI framework โ†’ Another new frameworkโ€ฆ

It never ends. ๐Ÿ˜‚

Learning new technology is important.

But things like:

Databases
Networking
Caching
Security
Architecture
Performance
Debugging

These concepts stay useful even when the technology changes.

5๏ธโƒฃ ๐—•๐—ฒ๐—ถ๐—ป๐—ด ๐˜€๐—ฒ๐—ป๐—ถ๐—ผ๐—ฟ ๐—ฑ๐—ผ๐—ฒ๐˜€๐—ป'๐˜ ๐—บ๐—ฒ๐—ฎ๐—ป ๐—ธ๐—ป๐—ผ๐˜„๐—ถ๐—ป๐—ด ๐—ฒ๐˜ƒ๐—ฒ๐—ฟ๐˜†๐˜๐—ต๐—ถ๐—ป๐—ด.

This took me some time to understand.

Being senior doesn't mean:

โ€œI know the answer to everything.โ€

Sometimes it means:

โ€œI don't know yet, but I know how to figure it out.โ€

And sometimes:

โ€œLet me ask someone who knows more than me.โ€

That's completely fine.

6๏ธโƒฃ ๐—ข๐—ป๐—ฒ ๐˜๐—ต๐—ถ๐—ป๐—ด ๐—œ ๐˜ƒ๐—ฎ๐—น๐˜‚๐—ฒ ๐—บ๐—ผ๐—ฟ๐—ฒ ๐—ป๐—ผ๐˜„ โ€” ๐—ต๐—ฒ๐—น๐—ฝ๐—ถ๐—ป๐—ด ๐—ผ๐˜๐—ต๐—ฒ๐—ฟ ๐—ฑ๐—ฒ๐˜ƒ๐—ฒ๐—น๐—ผ๐—ฝ๐—ฒ๐—ฟ๐˜€.

Earlier, solving a problem myself felt like an achievement.

Now, helping another developer understand the problem feels even better.

Because if I solve it once, the problem is solved.

If I help someone understand itโ€ฆ

they might solve the next 10 problems themselves.

And I think that's one of the biggest differences I've noticed as I've grown as a developer.

The funny thing about software development isโ€ฆ

๐˜๐—ต๐—ฒ ๐—บ๐—ผ๐—ฟ๐—ฒ ๐˜†๐—ผ๐˜‚ ๐—น๐—ฒ๐—ฎ๐—ฟ๐—ป, ๐˜๐—ต๐—ฒ ๐—บ๐—ผ๐—ฟ๐—ฒ ๐˜†๐—ผ๐˜‚ ๐—ฟ๐—ฒ๐—ฎ๐—น๐—ถ๐˜€๐—ฒ ๐—ต๐—ผ๐˜„ ๐—บ๐˜‚๐—ฐ๐—ต ๐˜†๐—ผ๐˜‚ ๐˜€๐˜๐—ถ๐—น๐—น ๐—ฑ๐—ผ๐—ป'๐˜ ๐—ธ๐—ป๐—ผ๐˜„. ๐Ÿ˜„

Still learning.
Still making mistakes.
Still debugging things.

Just getting a little better at figuring out why things break. ๐Ÿš€

Top comments (0)