Identify code best practices, discuss them with your team to define the practices most adapted to your context together.
Each developer identifies best practices (followed or not) in a few recent files, and can propose new ones. This is done in Promyze or in the developer’s IDE. Clean Code, Architecture, Testing, Performance, Security, … all topics can be addressed.
During a workshop retrospective, the team discusses the identified practices together. Each developer details and justifies his proposals. An open discussion starts, allowing to determine the choice most adapted to the project context.
If an identified practice does not achieve consensus in the team, a battle begins. Each member can then add his arguments for or against this practice and vote to implement it or not.
The practices created are centralized in Promyze and available from the IDE. Catalogs of practices allow you to organize them efficiently. They are updated and consolidated after each workshop, and can also be easily shared with other teams.
Each example identified in your code or refactoring suggestion is recorded in the practice description.
Promyze, the collaborative platform dedicated to improve developers’ skills through best practices sharing and definition
