clean code / semantic versioning
This commit is contained in:
parent
faf242e4ce
commit
825ab7de3c
@ -1188,6 +1188,7 @@ I just want to centralize my findings and bookmarks in a central location, and s
|
|||||||
* [GitHub](https://github.com/showcases/clean-code-linters) - Clean code linters
|
* [GitHub](https://github.com/showcases/clean-code-linters) - Clean code linters
|
||||||
* [Ansible Best Practises](https://github.com/enginyoyen/ansible-best-practises) - A project structure that outlines some best practises of how to use ansible
|
* [Ansible Best Practises](https://github.com/enginyoyen/ansible-best-practises) - A project structure that outlines some best practises of how to use ansible
|
||||||
* [Awesome Guidelines](https://github.com/Kristories/awesome-guidelines) - A curated list of high quality coding style conventions and standards.
|
* [Awesome Guidelines](https://github.com/Kristories/awesome-guidelines) - A curated list of high quality coding style conventions and standards.
|
||||||
|
* [Tom Preston-Werner](http://semver.org/) - Semantic Versioning 2.0.0
|
||||||
|
|
||||||
## Debugging
|
## Debugging
|
||||||
* [The Geek Stuff](http://www.thegeekstuff.com/2010/03/debug-c-program-using-gdb/) - How to Debug C Program using gdb in 6 Simple Steps
|
* [The Geek Stuff](http://www.thegeekstuff.com/2010/03/debug-c-program-using-gdb/) - How to Debug C Program using gdb in 6 Simple Steps
|
||||||
|
Loading…
Reference in New Issue
Block a user