I mentored people at CodeMentor. However, I am not able to continue mentoring because I do not have a good voice. I struggle to be on call for more than 15 minutes where I have to keep talking. I am a good listener.

I mentored two other people. One quit programming and did an MBA because he felt he can never become like me!

The other one is a successful QA who does testing using tools like Pupeteer, Selenium, Cypress, etc.

I should also develop patience when people ask silly questions!

I have been mentoring now for about 2 years. I was fortunate enough to mentor 5 students and forming a group called Madhacks. Madhacks is a community focused on spreading and sharing the knowledge of computer science.

Checkout (madhack.co)

I always love teaching and sharing my knowledge with others as much as possible and I always look forward on how I could make the teaching more interesting.

Now Madhacks along with Madlabs (madlabs.xyz) have created a project scaffolding tool for MEVN (Mongo Express Vue Node) stack called the MEVN-cli (mevn.madhacks.co) which is slowly growing.

At present I am planning onto a mission of reaching a wider group of students with a tool called Teachcode. Teachcode is a cli which helps students to learn programming all by themselves using a terminal in an interesting manner.

Checkout (github.com/madlabsinc/teachcode)

I am unofficially mentoring people for ~10 years now. Those are mostly people who are in different professions but for any reason (mostly boredom or financial) they want to change their career and become programmers. I usually teach them frontend web development because that skill tree is the easiest for getting the job asap.

My way of mentoring usually involves giving them tutorials (either book/documentation or YT videos) and then giving them tasks which correlate to the skills they learned so far. While they work on those tasks I provide help if they get stuck. After the task is done I am doing the code reviews and improving their coding as they learn. In this way they can see their progress through commits and we are also building their project CV on github which is IMO most important thing to showcase on junior job interview.

Also since I am working this pro-bono I always try to minimize my time by encourage my mentees to help between themselves (i usually make skype groups for them). Also I teach them to help themselves - proper usage of google search for answers, using tech forums, overcoming the fear to ask questions on stack overflow, attend meetups and presentations,...

Main thing I say to the ones I train is "pay it forward" - which means that they should pay me back by continuing to spread the knowledge and skills.

I consider my job as done when my trainees land their first programming job because at that point they will learn much more about programming on that job than from me on their spare time.

With this method I have had success rate around 15% so far - lot of people gave up for various reasons (life got in the way, they were not passionate about coding, they got better offer at their current career, they were lazy,...), but I am happy to say that all trainees who finished my course through the end (usually their last task is full fledged reactive frontend application) managed to find a job in the industry so there my success rate is 100%.

Also lately I don't want to exceed number of trainees more than 3 because I want to spend more time with my family. If someone new comes to me for mentoring and my capacity is full I forward them to one of my ex-trainees now colleagues :)

I've helped three beginners to get started with programming (one of them webdev), by sugesting topics, answering questions and making small projects together.

But two of them went on to other fields. So don't do what I did, I guess?

I can't really call myself 'a mentor' but I try to help people when they need as much as I can. But while doing that, I have never write the code for someone. I try to show pseudo code or show the way to solution and let them do the actual coding, to understand the problem and the solution. What I have learned last 25 years of hand-on-keyboard is making lots of mistakes, solving problems by myself with researching, asking questions and try-and-fails were the most teaching points and foundation of experience.