{"id":135,"date":"2016-12-04T10:30:38","date_gmt":"2016-12-04T10:30:38","guid":{"rendered":"http:\/\/www.cardiomaths.net\/?p=135"},"modified":"2016-12-04T17:30:30","modified_gmt":"2016-12-04T17:30:30","slug":"coding-style-guides","status":"publish","type":"post","link":"http:\/\/www.cardiomaths.net\/index.php\/2016\/12\/04\/coding-style-guides\/","title":{"rendered":"Some useful coding style guides"},"content":{"rendered":"<p>While I&#8217;m sure I don&#8217;t always follow this advice, using a coding style guide makes sense and was something I always stressed was essential when working in teams. Even when you are working on your own using a coding style guide generates code that is much easier to maintain.<\/p>\n<p>It turns out that Google publishes their own style guide, I quite like them and so I&#8217;ve published the links to them below (just the ones I&#8217;m most likely to use). All I was really missing was a style guide for Matlab and Julia so I&#8217;ve added a link to Matlab and Julia.org&#8217;s own.<\/p>\n<p>Google encourages the use of TODO comments in code, a nice and consistent way of marking areas of code that need improving (TODO(user)).<\/p>\n<p><a href=\"https:\/\/google.github.io\/styleguide\/Rguide.xml\">R style guide<br \/>\n<\/a><\/p>\n<p><a href=\"https:\/\/google.github.io\/styleguide\/shell.xml\">Shell style guide<\/a><\/p>\n<p><a href=\"https:\/\/google.github.io\/styleguide\/pyguide.html\">Python style guide<\/a><\/p>\n<p><a href=\"https:\/\/uk.mathworks.com\/matlabcentral\/fileexchange\/46056-matlab-style-guidelines-2-0\">Matlab style guide<\/a><\/p>\n<p><a href=\"http:\/\/web.mit.edu\/julia_v0.3.11\/.julia-483dbf5279.amd64_ubuntu1404\/share\/julia\/doc\/_build\/html\/manual\/style-guide.html\">Julia style guide<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>While I&#8217;m sure I don&#8217;t always follow this advice, using a coding style guide makes sense and was something I always stressed was essential when working in teams. Even when you are working on your own using a coding style guide generates code that is much easier to maintain. It turns out that Google publishes [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"http:\/\/www.cardiomaths.net\/index.php\/wp-json\/wp\/v2\/posts\/135"}],"collection":[{"href":"http:\/\/www.cardiomaths.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.cardiomaths.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.cardiomaths.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.cardiomaths.net\/index.php\/wp-json\/wp\/v2\/comments?post=135"}],"version-history":[{"count":5,"href":"http:\/\/www.cardiomaths.net\/index.php\/wp-json\/wp\/v2\/posts\/135\/revisions"}],"predecessor-version":[{"id":141,"href":"http:\/\/www.cardiomaths.net\/index.php\/wp-json\/wp\/v2\/posts\/135\/revisions\/141"}],"wp:attachment":[{"href":"http:\/\/www.cardiomaths.net\/index.php\/wp-json\/wp\/v2\/media?parent=135"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.cardiomaths.net\/index.php\/wp-json\/wp\/v2\/categories?post=135"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.cardiomaths.net\/index.php\/wp-json\/wp\/v2\/tags?post=135"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}