After you get your first job as a web developer, you'll realize there's so much more to it than you initially thought. There will be a learning cur...
For further actions, you may consider blocking this person and/or reporting abuse
Great advice, and I like this point especially:
One of the most common issues I've seen when working with junior developers is when they sometimes spend WAY too long trying to figure out a problem on their own without asking anyone for help. And then the stress just starts compounding as the deadline gets closer.
Often the obstacle is the fact that the codebase has idiosyncracies or the project documentation is unclear. That's when a quick conversation can clear things up almost instantly.
Yes! I think they're just nervous about looking like they don't know what they are doing.
Beginner devs: One thing to keep in mind is that you will get stressed. So when you do try and do something that is productive but also will help you get organised. Such as:
Other than that just remember: You are capable of finding the answer, but that doesn't mean help isn't the wrong way to go.
Good point with this article! Since I'm not a professional developer and only a few weeks ago I started applying for some jobs this is the exact thing that concerns me the most. How should I deal with pressure and deadlines when I'm not fully ready to perform the task?
Thank you, thank you, thank you!!
I'm really glad it helped! Good luck! Just try not to let the stress get to you.
Great article this is what i have been through when i was a junior dev, procrastination is bad for junior dev as they don't have full idea how that work will scale and later on the practical part they get to know that it's at-least lengthy if not challenging.
How do you estimate the time to completion for those iceberg tasks like the select option while you are new?
Here's a few ideas:
Thank you, the Codepen idea sounds like an exceptionally good idea.
Thank you very much for this great article.
I have a question about my situation: I'm the only developer in my workplace and specially lately I get struck very often with the new project based on new framework/language that I just start to learn.
In this case what is the best strategy to avoid to get struck?
I am in the same boat and feel for you. I find it easiest to go straight to reading the documentation compared to Dev/Medium tutorials or stack overflow.
I find Dev/Medium tutorials always give me environment issues or, stack overflow too, will get me started on the wrong foot in an unseen way.
This is something everyone needs to hear. Thanks so much!