Code quality has a practical impact on both your agility and the cost of development. You can’t change buggy code fast enough to be truly agile. Existing bugs can easily increase dev costs (and time) by 10x. You can't afford not to fix them. — Allen Holub
Don't abstract when you don't have to. Premature optimization often causes pain, results in bloated code, and fewer developers understand what is going on. Write tests instead so you can safely refactor when really needed.
Maintaining small amounts of duplicate code is much easier and less work than choosing the wrong abstraction.
Premature optimization is the root of all evil. — Donald Knuth
A cache is just a memory leak you haven't met yet. — Dave Cheney
While we expect this to be difficult when working with a distributed team and pull requests, we encourage all contributors to refactor whenever they see a specific issue, and they are working on related code anyways (so that you can validate if your changes are helpful). This way, there is no need for extra refactoring tasks or epics. Let's experiment and see how far we get with this.
Ugly code is not a problem as long as there are tests, there are no security issues, and it can be easily refactored later. Nobody needs beautiful code that doesn't work.
You have to go slow before you can go fast. Keep it simple. Done is better than perfect. Be pragmatic. Stay focused.
Feel free to think ahead, just don't code ahead. But also, don't feel the need to decide so many details ahead. Learn enough to get started and build only what you need. — J. B. Rainsberger
Test Coverage ¶
Test coverage is a useful tool for finding untested parts of our codebase. Test coverage is of little use as a numeric statement of how good our tests are.
We strive for complete test coverage. Code that cannot be tested is flawed.
A coverage log file created by the Go test runner is automatically sent to Codecov every time our
develop branch was successfully built and tested on Travis CI. Codecov provides a beautiful UI for displaying coverage reports and renders a badge showing the current test coverage. Custom settings for our report are located in codecov.yml. For example,
range: 50..90 means the badge will be green if coverage is >= 90% and red if it is <= 50%.
Quality Reports ¶
goreportcard.com finds typical issues in Go source code
Not every issue reported by tools is really important and needs to be fixed instantly. Use reports for inspiration when you need some.