The software industry has one of the highest turnover rates globally, 10-15% on average in past years. Thanks to organic growth or fundraising, several digital companies significantly increase their teams every month.
In that context, developers leaving or joining a team happens regularly, and the onboarding process of software engineers is unavoidable.
Few facts about onboarding:
In other words, a great onboarding experience has a positive impact on recruits’ wellness and retention in the company. Still, according to the Harward Business Review, 22% of companies don’t have an onboarding process. Dangerous, right? 🔥
You’ll find plenty of content on the Internet on that topic, including checklists, tips, and advice to create a great onboarding experience.
Among the points to address:
Let’s focus on this last topic now! 🚀
An efficient onboarding process on best practices will definitively save you time for your first code reviews with your new developers.
We illustrated in other posts how you could use your favorite IDE (VS Code, Visual Studio, JetBrains suite, or Eclipse) or Web browser (for GitLab, GitHub, Bitbucket, and Azure integration) to define with your team your best practices, on any topic you’re interested in: Clean Code, language, framework, security, performance, architecture, ….
If you use Promyze for that purpose, you’ll end up with a repository of best practices, each of them documented with either positive or negative examples (the “do/don’t” ):
Now, assume Lucy is joining your team today, and she needs to get familiar with your codebase and the standards and practices you use every day. Without Promyze, this is often managed – not without difficulty – using Wiki tools. Using Promyze, you get documentation with concrete illustrations from your codebase.
So at first glance, you could think that Lucy could go through each practice one by one to discover them. But only reading might be boring and not 100% efficient in a learning context.
Promyze has this “Discovery Workshops” feature, which lets you create challenges based on your existing repository of best practices. You’ll define workshops on the topics that are relevant to your context.
The concept is straightforward:
Here is an illustration of how to create a Discovery Workshop:
Assume now you’d like Lucy to run this Workshop. On the right side of the screen will be listed all the practices to identify. The green color means the practice was applied correctly in the code, while the orange color means it did not. Using text selection, she’ll attempt to find the matching locations:
Once she’ll finish the workshop, she can access the Workshop correction and compare her proposals with the correct answers:
Then, she’ll get the results to see what she managed to find and where she was wrong. If we take a step back, such a Discovery Workshop:
Want to get started and create your first Workshop? Get started on Promyze.com
Promyze, the collaborative platform dedicated to improve developers’ skills through best practices sharing and definition