A practical tip for self-improvement: If you're using JetBrains IDEs, make it a habit to never commit code without reviewing and addressing the IDE's soft warnings and code improvement suggestions. This built-in static analysis can serve as a basic code review mechanism and help maintain code quality standards
This, but also learn to configure other linters, not only things bound to a specific IDE. Learn from the errors that linters raise, their documentation usually has a "rationale" section for each rule.
Ideally you should also run those linters in CI/CD. When a new member joins the team, they will get CI/CD linting for free, which will save you a ton time for each new team member
