I will share my approach to get a high-level overview of the quality of any Unity project. As a result, I will be able to highlight areas of the project for a deeper review. During my last 5 years as technical lead in Playtika, I had to review different Unity projects and define areas for improvements in technical roadmaps. These markers really take me 10 minutes and might be your first step before deep-diving into a new for your project.
Let's see what can be discovered from these areas:
- Basic characteristics of the project
- Code statistics of the project
- Technical Spec/Restrictions of the Project
- Project structure overview
- Manifest, editor settings
- Third-parties check
- Tests and Test runner
Basic characteristics
- Size of the project — the larger the size, the more difficulties may arise from development experience, quality in general, level of debt, etc. A few GBs for the newly fetched project is a sign that it will require additional support from the team to make a comfortable workflow inside the project. As well as will also require additional hardware capabilities on CI/CD to be good at building pipelines.