diegoloop

17 ms·

31.
Swift coding style – Keywords(codingstyleguide.com)
1 points by diegoloop 12y ago|0 comments
32.
Swift coding style – Identifiers(codingstyleguide.com)
1 points by diegoloop 12y ago|0 comments
33.
Apple Swift coding style – How to Read the Grammar(codingstyleguide.com)
1 points by diegoloop 12y ago|0 comments
34.
Ruby code style – Never use for, unless you know exactly why(codingstyleguide.com)
1 points by diegoloop 12y ago|0 comments
35.
C++ style: Casting – Dont use other cast formats like int y = (int)x;(codingstyleguide.com)
1 points by diegoloop 12y ago|0 comments
36.
by diegoloop 12y ago
Thank you for the info @binofbread, I didn't know that. Could you please send me a screenshot to diegoloop@icloud.com? That would be great! Thank you!
37.
by diegoloop 12y ago
I came up with this idea: http://codingstyleguide.com Wouldn't it be nice to have a repository of many Style Guides, where the users can vote on each to decide which one is better - some kind of mixture of Quora, StackExcha
38.
CSS code style – Opening brace of the declaration block on same line as selector(codingstyleguide.com)
1 points by diegoloop 12y ago|0 comments
39.
CSS coding style – Each selector gets it's own line(codingstyleguide.com)
3 points by diegoloop 12y ago|0 comments
40.
Coding style (Java): Avoid abbreviations in names(codingstyleguide.com)
2 points by diegoloop 12y ago|0 comments
41.
Ask HN: What's the best programming book you've read recently?
93 points by diegoloop 12y ago|90 comments
42.
Java coding style: Use Standard Brace Style(codingstyleguide.com)
2 points by diegoloop 12y ago|0 comments
43.
PHP best practices – String Concatenation(codingstyleguide.com)
1 points by diegoloop 12y ago|0 comments
44.
Rust programming style: Variable, Function, Module and Type Names(codingstyleguide.com)
1 points by diegoloop 12y ago|0 comments
45.
by diegoloop 12y ago
I also found this useful since it has more diversity of content: http://codingstyleguide.com/lang/ruby
46.
Programming style(HTML): Don't "close" void elements (codingstyleguide.com)
1 points by diegoloop 12y ago|0 comments
47.
by diegoloop 12y ago
Thank you @collyw! Still too much guidelines to post... The idea is to have different solutions for every writing convention in any programming language.
48.
by diegoloop 12y ago
That's why I came up with the idea to make a huge repository ( http://codingstyleguide.com ) of programming conventions, "best practices", etc for any language. Where anyone (scientist, experts and newbies) can visi
49.
CoffeeScript style: Dont use parentheses when declaring functions with no args(codingstyleguide.com)
1 points by diegoloop 12y ago|0 comments
50.
JavaScript style: Eval is Evil(codingstyleguide.com)
2 points by diegoloop 12y ago|0 comments
51.
JavaScript style: Programs should be stored in and delivered as .js files(codingstyleguide.com)
1 points by diegoloop 12y ago|0 comments
52.
Python style: Testing for Truth Values(codingstyleguide.com)
1 points by diegoloop 12y ago|0 comments
53.
Java style: Do not Catch Generic Exception(codingstyleguide.com)
1 points by diegoloop 12y ago|0 comments
54.
JavaScript style: Always use the curly braces, even when optional(codingstyleguide.com)
1 points by diegoloop 12y ago|0 comments
55.
JavaScript style: always use semicolons(codingstyleguide.com)
7 points by diegoloop 12y ago|1 comments
56.
by diegoloop 12y ago
Yes but in most of the cases it's better to use === operators. I mean, they both are correct. It's just a matter of style
57.
by diegoloop 12y ago
Agreed, here are more JS styles that might be interesting for you: http://codingstyleguide.com/lang/6/javascript
58.
JavaScript: Use === Instead of ==(codingstyleguide.com)
2 points by diegoloop 12y ago|4 comments
59.
Find the dark side for your next trip -Sunny Boy localizes the seat in the shade(itunes.apple.com)
1 points by diegoloop 12y ago|0 comments
60.
The "Practical Guidelines and Best Practices" chapter in most programming books(codingstyleguide.com)
1 points by diegoloop 12y ago|0 comments

More ›