- Ratio of code:documentation INSIDE the source code
- Directory structure depth is “just right”; not too deep nor too shallow
- Number of dependencies is “just right”; don’t build things yourself, but also don’t import the whole world
- TTLD (Time To Local Dev); how simple is the getting started guide in terms of copy-pasta commands + automation + the right amount of context + easy-to-use tooling
- Code culture; follow industry best practices and make it clear where & why you deviate
My personal favorite one: `make todo_list`
We use keywords (TODO, OPTIMIZE, HACK, etc…) through the codebase and make them easily searchable with make helpers.
Ref: https://github.com/pokt-network/pocket/blob/main/Makefile#L5...