Why does onboarding matter? The software industry has one of the highest rates globally, 10-15% on average in . Thanks to organic growth or fundraising, several digital companies significantly increase their teams every month. turnover past years In that context, developers leaving or joining a team happens regularly, and the onboarding process of software engineers is . unavoidable Few facts about onboarding: It can take up to for a new programmer to reach optimum productivity seven months New employees who go through a structured onboarding program are more likely to be with the organization after three years (Source: Digitate) 58% Organizations with poorly-handled onboarding are twice as likely to cause new hires soon (Source: Allied) to seek new opportunities In other words, a great onboarding experience has a positive impact on in the company. Still, according to the Harward Business Review, 22% of companies don’t have an onboarding process. Dangerous, right? 🔥 recruits’ wellness and retention 👩🏻‍💻 What’s essential when onboarding a developer? 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: The culture, business, history, values, organization, … company The goal, core business, people/responsibilities, the incoming milestones, … project The of the project (not exhaustive): technical environment the codebase and its architecture (DDD ?) how to set up a dev environment, build and run the app the development workflow (TDD ?) the CI/CD process (the “DevOps Big Pic”) 📑 the coding standards and best practices Let’s focus on this last topic now! 🚀 An efficient onboarding process on best practices will definitively save you time for your first with your new developers code reviews 🔍 Help new developers discover your best practices We illustrated in other posts how you could use (VS Code, Visual Studio, JetBrains suite, or Eclipse) or (for GitLab, GitHub, Bitbucket, and Azure integration) to , on any topic you’re interested in: Clean Code, language, framework, security, performance, architecture, …. your favorite IDE Web browser define with your team your best practices If you use for that purpose, you’ll end up with a repository of best practices, each of them documented with either positive or negative examples (the “ ” ): Promyze 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 - - using Wiki tools. Using Promyze, you get documentation with concrete illustrations from your codebase. not without difficulty So at first glance, you could think that Lucy could go through each practice one by one to discover them. But in a learning context. only reading might be boring and not 100% efficient 🌟Turn your knowledge base into interactive challenges Promyze has this “ ” 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. Discovery Workshops The concept is straightforward: Build a list of best practices you want to include in your Workshop Select for each practice some examples and counter-examples from the practice documentation. Name your Workshop; you’ll probably include its topic in it (e.g., “React) Each user will have to find in the source code of the Workshop where some best practices have been followed or not. 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: Brings an challenge for Lucy and improves her onboarding experience interactive Offers a of where Lucy stands regarding your best practices and which points you should focus on with her better overview Is an automated and thus tool you can use for your future onboardings while saving time and gaining efficiency. repeatable Want to get started and create your first Workshop? Get started on Promyze.com Also Published here

Discovery

ORANGE

2022 - HackerNoon Contributor of the Year - Code Quality

2022 - HackerNoon Contributor of the Year - Developer Tools

Get started now!

Nominated for 2022 - HackerNoon Contributor of the Year - Developer Tools

Nominated for 2022 - HackerNoon Contributor of the Year - Code Quality

Too Long; Didn't Read

Developers: Build Less. Deliver More. [Learn how]	

Onboard New Developers with Better Coding Practices

Too Long; Didn't Read

Companies Mentioned

Promyze

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

Onboard New Developers with Better Coding Practices

Too Long; Didn't Read

Companies Mentioned

Promyze

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

RELATED STORIES