Close collaboration is essential not only to what we do at Elsewhen, but for efficient development and delivery of digital products in any context. To that end, it’s essential that best practices are not only established, but observed, iterated on and developed with the same speed as the tools they are designed to assist. While this isn’t a controversial position, it’s not often adopted as a practice nearly as often as it’s publicly espoused.
After all, maintaining someone else’s code is not a smooth process. It takes time to observe the project (folder structure, naming, dependencies, scripts etc.), find the pattern and develop the new feature in harmony and consistency with the existing code. Different developers use different styles which are derived from their different tastes. They may work on a project together or pick up someone else’s work. In both cases, having a common ground is essential.
You can view the Project Guidelines on Github here.