Embedded Files
There are my coding styles compiled after contributing back to the open-source communities. Some of the sources are from various projects from Google and some are from Linux communities.
What I normally do is that I maintain a version of mine for all the styles and then learn and adapt new styles whenever I meet a new one. As for the judgement for choosing the styles, I based on sensible, and factual rationality. Each adopted styles should have its own rationality.
Organization
Organization
There are 2 main set of sub-sections:
- In General - the adopted version that is applicable to all
- Language specific - the language specific version that is applicable to a particular language, addition or override the "In General" section.
Sub-Sections
Sub-Sections
If there are any sub-sections inside a language / in general, those are critical and mistakes that are easily made. Hence, do look out for them to avoid creating a catastrophe.
References
References
- https://www.kernel.org/doc/html/v4.10/process/coding-style.html
- https://dave.cheney.net/practical-go/presentations/qcon-china.html
- http://google.github.io/styleguide/
- https://github.com/golang/go/wiki/CodeReviewComments
- https://golang.org/doc/effective_go.html
- https://www.cs.cmu.edu/~charlie/courses/15-214/2015-fall/slides/02a-design-for-change.pdf
- https://google.github.io/styleguide/jsguide.html
- https://sass-guidelin.es/
- https://netmidas.com/blog/sass-best-practices-avoid-frustrated-developer-beginner-level/
- https://www.hongkiat.com/blog/sass-tips-tools-for-developers/
When you're ready, feel free to visit the sub-sections. I suggest you should start with "In General".
Page updated
Google Sites
Report abuse