4 ms·
- Automated testing running on each PR - Having a dedicated Quality team - Ensuring everyone is on the same page, from the lowest level (coding standards) to
by egman_ekki 5y ago
- Automated testing running on each PR
- Having a dedicated Quality team
- Ensuring everyone is on the same page, from the lowest level (coding standards) to mid level (discussing tasks before implementing them) to meta level (principles for development, building culture)
- Rewarding bold moves and experiments, giving people freedom to be creative
- Leveraging the wisdom of the Open Source community
- alexchamberlain 5y agoThe 2nd and 3rd points seem somewhat at odds? How do you balance team discussion with encouraging individuals to experiment and push the boat forward?
- egman_ekki 5y agoThe important part for me is to make sure everyone understands _what_ needs to get done, not necessarily prescribe _how_ to do it. But I agree it can be fuzzy. Generally I want folks to be aligned and super clear on what we're trying to do, because if everyone understands it differently, we're all pulling in different directions.