Do you teach language learning? Principles of software architecture? You have certainly defined a guide to properly apply these principles.
Moreover, you reuse these good practices through different training courses.
Promyze allows you to define these good practices, categorise them in profiles and easily reuse them for your different training courses.
Good development practice is often explained with simple and generic examples, which has certain limitations in real project cases.
Their understanding proves more effective if several concrete examples of implementation and counter-examples are included in the documentation.
With Promyze, you can identify these examples from the code produced by your students or your own code.
Whether they work alone or in groups, ensuring that your students have assimilated good practice requires investment and support.
Promyze's Craft Workshops make it easy to keep track of the product code by centralising the work produced by your students.
Collective retrospectives make it possible to capitalise on the dissemination of knowledge and the increase in skills of each student.
Code review is a practice recognised for its added value in maintaining a clear and comprehensible code for the entire team, as well as for preventing the risk of bugs. Promyze offers collaborative workshops to identify the best practices to be implemented on a project, in line with the pedagogical content made available to them. These interactions, where everyone has a say, enable working methods to be harmonised.
Taking a step back from the product code and setting up rituals dedicated to the quality of the developments carried out strengthens trust and links between developers. Craft Workshops are collective thinking exercises that open up free discussions between team members. The tool is also a support to help trainers identify possible improvements in the code, and accompanies them in the exercise of knowledge transmission, thanks to a lively documentation of good practices.
The quality of the code is essential to maintain a good level of motivation of the developers on a project, to prevent the risk of bugs and regressions. A quality code, well tested, makes the workflow more efficient and reinforces the feeling of value creation. As an instructor, you pass on these principles to your students. Promyze is there to support you in this process by implementing these principles throughout your courses.Discover a feedback from Promyze at the University of Bordeaux
The risk of bugs, exploding maintenance costs and loss of team motivation are all negative impacts linked to poor management of a project's technical debt. Being aware of the medium and long term impact of the technical choices made by the team is a valuable faculty for developers.
Controlling and monitoring technical debt requires a certain rigour and organisation, in order to anchor this management in team processes. Promyze supports teams in monitoring the evolution of their technical debt, and automates the implementation of action plans to suggest relevant operations to be carried out in the source code.
Promyze raises students' awareness of coding rules and accompanies them throughout their course to offer them a relevant and caring look at their development practices. These skills will be all the more appreciated at the beginning of their career.