Codebase Properties

[craigjbass]

• [ ] One click deploys
• [ ] Low probability of error in deployments
• [ ] Reproducible deployments
• [ ] Reproducible development environments
• [ ] Understand usage of software at a glance
• [ ] Ability to defer technology decisions
• [ ] Code is the documentation
• [ ] Code Reveals Intent not Details
• [ ] Shared understanding of the domain written as expressive code
• [ ] Evolutionary Architectures
• [ ] Ability to *scout without fear
• [ ] Almost impossible to break existing behaviour (semantically stable test suites)
• [ ] Fast-executing ability to check that existing behaviour is still working correctly
• [ ] Non-brittle testing of the behaviour of code that received data from external services
• [ ] Non-brittle testing of the behaviour of code that sends data to remote services
• [ ] Reduced churn of files/functions/modules/classes
• [ ] No Tech-Debt Epics
• [ ] Single tech ecosystem includes multiple independently deployable components
• [ ] Sustainable Pace

[craigjbass]

Taken from a list that was around when Learn Tech started

[antdking]

(hijacked, changed list into a checklist, so we can tick off what's there)

[booyaa]

It would be good to have this extracted as a breakout doc in reference as we do with ruby. Trying to think where it would appear in the checklist, in an existing section or in a new section called Code quality? You could then bring Testing, Linting and local Dev into this new section.