In yesterday’s email, I said “Code Review backed by Code Standards and Style Guides” was the second most important thing a SuiteScript team needs for long-term success, so let’s discuss it.
Code review is a crucial part of a cohesive development team. When used effectively, there is no better method for creating consistent, readable, maintainable code bases.
In order to be used effectively, however, everyone on the team has to know what constitutes “good code” for that team. The best way I’ve found to do that is to establish, document, and onboard team members with code standards and style guides.
There are a ton of amazing resources which you can find on these topics, and many teams/companies actually publish their standards. Here are a few of my favorites:
- About 17.7 million other pages
If you’ve already implemented the most important component, source control, and you’re using an effective branching scheme like we discussed in that email series, then your merge/pull request stage is the ideal place for code review to take place.
What has your experience been with code review and standards?