Long time software architect, CTO Authress, creating application security plug-ins for any software application with Authress. Talk to me about security in microservices or service authorization.
This article is awesome, and also highlights to the catch-22 of learning. You have to already know about dev.to and the community to get these insights. This is really a message senior engineers need to understand and help new juniors ho find their way.
They probably have never heard of stack overflow, or dev.to, or any of those awesome resources that you've been using. The first step is for you to share these fountains of knowledge so that they can grow quickly into the best engineers.
This is where "team" becomes really important. Having someone sit by themselves won't result in a success. You need a team working together to help educate and coach juniors. How to pull that new person into your process? How do you onboard? And even after they are "onboarded" how do you know they are being successful? Perhaps you are a great manager and team lead, and you have the perfect strategy for that, but likely everyone can use some help here. You need to find your tools to be helpful:
Alignment (How to make sure everyone knows what's happening in the business and the team, and why)
work tracking (What is currently being worked on, and what is the state)
overall team happiness and engagement (Do you know if someone feels unsupported in the team?)
feedback loops (How do you know when there is a problem, and get insight on how to fix it)
These are the most important.
You should have a tool that helps with each one of them, ideally you lean on the industry to support you in everyone's growth.
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.
This article is awesome, and also highlights to the catch-22 of learning. You have to already know about dev.to and the community to get these insights. This is really a message senior engineers need to understand and help new juniors ho find their way.
They probably have never heard of stack overflow, or dev.to, or any of those awesome resources that you've been using. The first step is for you to share these fountains of knowledge so that they can grow quickly into the best engineers.
This is where "team" becomes really important. Having someone sit by themselves won't result in a success. You need a team working together to help educate and coach juniors. How to pull that new person into your process? How do you onboard? And even after they are "onboarded" how do you know they are being successful? Perhaps you are a great manager and team lead, and you have the perfect strategy for that, but likely everyone can use some help here. You need to find your tools to be helpful:
These are the most important.
You should have a tool that helps with each one of them, ideally you lean on the industry to support you in everyone's growth.