On some teams, writing good code feels like swimming upstream
On some teams, writing good code feels like swimming upstream.
I've joined teams with:
No CI
No types
No linting
Lax code reviews
No automated tests
Rampant copy/paste
No coding standards
No definition of done
Inconsistent patterns
On teams like this, writing good code is HARD.
When writing good code is hard, it's time to pause, and discuss how to make it easier.
The items above are like guardrails on a highway. Or good brakes on a sports car.
If we want to move fast, we need safety mechanisms. This assures we can move fast, safely.
Also, every project has momentum.
If a project starts without basic "best practices" in place, it's hard to change course. Especially given competing priorities.
The solution? Balance delivering features with improving practices.
Get a little better, every week.