Destroyed Coding guideline (markdown)

Coding-guideline.md

@@ -1,8 +0,0 @@
-1. Don't re-invent wheel. Look at std and boost first 
-2. Try to keep code in header files. Keep in mind you class my become a template later on. Use cpp files in case of cross-references
-3. If there is the same functionality both in std and boost, use std
-4. Use C++ 11 features, it makes code smaller and more readable
-5. Before implementing optimized assembly code, make sure there is a default implementation for other platforms
-6. Don't use additional dependency unless it's absolutely necessary. Std, boost and crypto++ should cover most of it
-7. Don't create extra thread just for waiting for some resource, try async operations instead
-