mirror of
https://github.com/zaphar/jeremy.marzhillstudios.com.git
synced 2025-07-21 19:29:48 -04:00
31 lines
519 B
YAML
31 lines
519 B
YAML
|
title: Top X Design/Coding Principles
|
||
|
|
time: 2009-08-29 00:16:37
|
||
|
|
tags:
|
||
|
|
- Site-News
|
||
|
|
- coding
|
||
|
|
- principles
|
||
|
|
content: |
|
||
|
|
Design/Coding rules
|
||
|
|
|
||
|
|
1. Data and Operations should be seperate
|
||
|
|
|
||
|
|
2. Workflows are awesome
|
||
|
|
|
||
|
|
3. Work from the outside in
|
||
|
|
|
||
|
|
1. Then from the Inside out
|
||
|
|
|
||
|
|
4. TDD TDD TDD
|
||
|
|
|
||
|
|
5. Keep the IO partitioned and at the edges
|
||
|
|
|
||
|
|
6. API's need to be *tight
|
||
|
|
|
||
|
|
1. More Permissive == more Headaches
|
||
|
|
|
||
|
|
2. Fuzzy states are bad
|
||
|
|
|
||
|
|
7. Every if has an else
|
||
|
|
|
||
|
|
8. Boilerplate is bad (boring to review hard to get right)
|