2020-04-12 10:56:18 -04:00
|
|
|
+++
|
|
|
|
|
title = "Top X Design/Coding Principles"
|
|
|
|
|
date = 2009-08-29T00:16:37
|
|
|
|
|
in_search_index = true
|
|
|
|
|
[taxonomies]
|
|
|
|
|
tags = [
|
|
|
|
|
"Site-News",
|
|
|
|
|
"coding",
|
|
|
|
|
"principles",
|
|
|
|
|
]
|
|
|
|
|
+++
|
2020-04-12 09:34:11 -04:00
|
|
|
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)
|
