When I was starting out my first junior position I was really good at Regex. I ended up becoming the go-to guy for complex database migrations since I could convert a huge C# "script" into a really simple SQL script that used Regex to find certain patterns and convert them into the required formats, etc.
These SQL scripts would do the job in a fraction of time (like days down to hours or hours down to minutes).
Eventually, I became the go-to for front-end stuff.
Then other stuff after that.
One of the main things I've gleaned from my career is that you need to be the "go-to" for something in order to stick out.
Sometimes is just a matter of discovering a gap in knowledge on your team - and filling it!
As you said Ali, get the fundamentals down.
I'd add "...then find what gap exists in your team's knowledge and learn learn learn learn!"
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I love points:
When I was starting out my first junior position I was really good at Regex. I ended up becoming the go-to guy for complex database migrations since I could convert a huge C# "script" into a really simple SQL script that used Regex to find certain patterns and convert them into the required formats, etc.
These SQL scripts would do the job in a fraction of time (like days down to hours or hours down to minutes).
Eventually, I became the go-to for front-end stuff.
Then other stuff after that.
One of the main things I've gleaned from my career is that you need to be the "go-to" for something in order to stick out.
Sometimes is just a matter of discovering a gap in knowledge on your team - and filling it!
As you said Ali, get the fundamentals down.
I'd add "...then find what gap exists in your team's knowledge and learn learn learn learn!"