Large community projects introduce constraints on how we program. Our biggest assets aren’t the hardware we run on or the language we use – it’s each other. How can we code in ways that respect each other and capitalize on that “asset” of the contributor-base? In this talk, we’ll discuss techniques and patterns which may not be intuitive from our own learning journey but which foster quality and overall project health.