This handbook page documents best practices how Developer Evangelists can help wider community members with mentoring and coaching.
GitLab Developer Evangelists actively engage with mentoring wider community members. The team's time is limited with our many activities, please understand when we decline a request. Polywork and other platforms can help finding mentors.
If the career path is to becoming a Developer Evangelist, the Developer Evangelism handbook provides many resources.
Engineering and coding sessions depend on the knowledge and focus area of the mentor.
Other examples are:
Document feedback and learnings in the handbook.
Make it a coffee chat with an agenda, following GitLab communication best practices.
1. Good vibes 1. Asks 1. Discussion
Start drafting talk ideas in a dedicated Google doc for each topic, and discuss the story and technologies in 1:1s. Add thoughts async, and share suggestions directly.
Organisation and workflow tips:
suggestingmode in the Gdoc and provide suggestions with all thoughts. Encourage the mentee to review the suggestions, and accept if reasonable. This workflow will enable mentees to take feedback from everyone in the future.
Tip: Talks are stories that evolve each time they are told. Think of a rock band giving a concert, each song is a little different when played live. The same applies to a talk story - iterate on talk questions and feedback, and also add new learnings and technologies over time. Events that accept a talk do not have the same audience and new folks can learn from talks.
Events and CFP forms collect different information, and also have different character limits for abstracts, etc. Iterate on collecting all details in a Google doc for the abstract as a single source of truth.
Example Gdoc for Michael's talk "Confidence with Chaos for your Kubernetes Observability"
Mentoring usually happens in 1:1 conversations, building trust and relationships, with optional public sharing. Coaching can happen in private and public, and can involve different types of short or long term help.
Engage with public replies in Twitter threads, LinkedIn posts, etc. and offer coffee chats or private conversations to wider community members who seek for advice. Listening to the story and plans helps with making suggestions efficiently, and builds trust and relationships too.
Developer Evangelists are encouraged to help with
How do I know when I'm showing signs of burnout?
Getting started in the cloud-native community with a huge landscape of tools to understand can be overwhelming. Learning technologies and frameworks, from Kubernetes to beyond, requires guidance and a plan for individual growth.
Michael had a coffee chat with Edidiong Asikpo who started her cloud-native journey as Developer Advocate at AmbassadorLabs in 2021. They discussed a learning plan as a DevRel in cloud-native, and shared ideas on demo deployments, learning with Observability, and also looked into the Developer Evangelism social media handbook.
In 2022, Edidiong shared her promotion to Senior Developer Advocate, responding to Michael's wishes:
The conversation we had when I started my journey in the Cloud Native space gave me the context I needed to learn and improve my skills. Thank you.