Six good tips for coding with others
-
Finish your code before moving on. Otherwise you’re going to have compounding technical debt.
-
Enforce standards for formatting. Use Linters. These expose low quality code faster and make rework much easier. Discipline = Freedom.
-
Document your patterns. Use a Markdown file or a Wiki to document how you do things like access your database.
-
Review new patterns early. Publicize them to the team for feedback.
e.g. - a new developer brings on their own access pattern to access a database, but doesn’t tell anyone about them using it. This pattern starts to show up around the code base, but it isn’t flexible enough to meet changing requirements.
-
Never expose refactoring to customers. That’s the developer’s job to handle. If the Customer is aware of it, they’ll try to control it. They’ll force you into bad situations.
-
Give yourself extra time for uncertainty. Give yourself extra time for documentation. Don’t fall prey to Unknown Unknowns and the Planning Fallacy.