Focus
There is too much noise out there, especially in the web dev area the ecosystem is so large that it's hard to find a direction. Keep evolving but master a skill/library before moving to another one, the devil is in the details and it takes a time to get there (reaching the limitations of a system, process, framework, language etc).
Steal the craftsmanship
Having a master or seniors around you will boost your career, if not find ones or quit your job, no junior should work alone on a project, is a loss-loss situation.
Like any physical craft, you should observe the senior practitioners, example if you are a web dev you can see a live/coding/panel with Dan Abramov and see first hand how a couple of technologies can boost your productivity 1000%.
Don't compromise (too much)
There is a fine line which you'll soon grasp, between being a professional and just a "worker that does tasks". If you work in a technical Env you're lucky, the guys in charge of the "tasks" know about and appreciate software methodologies (like automatic testing and post mortem team meetings to name a few), if not you have to struggle with the bussiness managers, trying everyday to improve your workflows.
You will soon learn how and when to say NO, sometimes what is good for you and your future or your project is not what the managers ask of you (basic example work overtime, apply dark patterns etc).
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.
All the good advice were already taken 🤠
Focus
There is too much noise out there, especially in the web dev area the ecosystem is so large that it's hard to find a direction. Keep evolving but master a skill/library before moving to another one, the devil is in the details and it takes a time to get there (reaching the limitations of a system, process, framework, language etc).
Steal the craftsmanship
Having a master or seniors around you will boost your career, if not find ones or quit your job, no junior should work alone on a project, is a loss-loss situation.
Like any physical craft, you should observe the senior practitioners, example if you are a web dev you can see a live/coding/panel with Dan Abramov and see first hand how a couple of technologies can boost your productivity 1000%.
Don't compromise (too much)
There is a fine line which you'll soon grasp, between being a professional and just a "worker that does tasks". If you work in a technical Env you're lucky, the guys in charge of the "tasks" know about and appreciate software methodologies (like automatic testing and post mortem team meetings to name a few), if not you have to struggle with the bussiness managers, trying everyday to improve your workflows.
You will soon learn how and when to say NO, sometimes what is good for you and your future or your project is not what the managers ask of you (basic example work overtime, apply dark patterns etc).