Please Visit: http://ift.tt/1ajReyV
segment - Our Engineering Team's Best Practices
1. It’s easier to combine than to split apart.
2. Explicit is better than implicit.
“Clever” code usually means “complicated” code. It’s hard to search for, and tough to track down where bugs are happening. We prefer simple code that’s explicit in it’s purpose rather than trying to create a magical API that relies on convention (go’s lack of “magic” is actually one of our favorite things about it).
3. It doesn’t ship without metrics and tests.
4. Cut scope aggressively.
5. Maintain a single code path.
6. Create rapid prototypes.
7. Know when to automate.
8. Aim to open source.
9. Solve the root cause.
10. Design models by concern.
http://ift.tt/1T49Efn
from Public RSS-Feed of Jeffery yuan. Created with the PIXELMECHANICS 'GPlusRSS-Webtool' at http://gplusrss.com http://ift.tt/1JZCKg0
via
LifeLong Community
