Coding for uncertainty
1 like1,010 views
The document discusses coding best practices for building applications that are durable, flexible, and fast. It recommends following the twelve-factor app methodology, including splitting apps into separate codebases, using the database as a fortress, and refactoring code mercilessly. Developers are also advised to use behavior testing over unit testing, keep models small with many ports, and extract generic code into gems.
Coding for uncertainty
- 1. CODING FOR UNCERTAINTY @SUBELSKY
- 2. BACKGROUND
- 3. THE OBSESSION: DURABILITY / FLEXIBILITY / SPEED
- 6. 12factor.net
- 8. TL;DL
- 9. USE 12 FACTOR ARCHITECTURE
- 10. LESS UNIT TESTING*, MORE BEHAVIOR TESTING
- 11. KEEP MODELS SMALL, USE LOTS OF POROS
- 12. SPLIT YOUR APP INTO SEPARATE CODEBASES
- 13. USE THE DATABASE AS A FORTRESS
- 14. USE SSL IN YOUR DEV ENVIRONMENT
- 15. HANDOVER DEVOPS TO 3RD PARTY SERVICES
- 17. RUTHLESSLY EXTRACT GENERIC CODE INTO GEMS
- 18. HAVE A rake deploy COMMAND IN EVERY PROJECT
- 19. HAVE A rake install COMMAND IN EVERY PROJECT