you should review every pull request of your team
- each pull request will make understand what everyone in your team is working on
- it will ensure you keep consistency of file location, and code patterns
- it will catch bugs/regression early on
- it will teach the best way to solve the problem
you should ensure consistency of the code base
you should pair programming with all devs of your team
- pair programming is a good way to show how you work, and your shortcuts
- you can also see what the dev is doing wrong, even tiny actions that matters in the long run
you should optimize dev experience (make ci faster, make hot reload faster, make things easier)
- make build and rebuild faster
- use react fast refresh - awesome for pixel perfect
- paralelize your tests - https://sibelius.medium.com/reduce-testing-and-building-time-in-monorepos-5843b63972b
you should make things easier to devs (i18n, tests, lint, lint-staged, types)
- adding a new test should be as things as coding something else
- adding a new i18n string should be fast and easy
- IDE should provide fast feedback on eslint and types errors/warnings
you should unblock issues
- check if the issue is well written
- check if something is missing (api, design, business logic)
- check if the developer that will do the issue have the same understand of you and the other stack holders
increase difficult of tasks incrementally
- in the beginning you should help a lot the developer (even a bit of middle management), they need to learn the code, they need to learn about business
- as the dev get used to the codebase, product and business, give him/her harder tasks, and help less. give more responsability
- show the problem, and let the developer provide the solution, let him/her think and own the issue
explain the motivation
- explain why we are doing something
- show how this fit in the big picture of the product/company
- motivation brings a meaning to work
this list will will evolve overtime
comment of how to improve it