jslint

The repo that helped me learn to developer is JSLint. This influenced my thinking on code organization more than all other facets combined. Please note though that JSLint has changed directions on a couple things since I started learning programming in 2008. * https://github.com/douglascrockford/jslint The repository that taught me about parsers, code style, and algorithms was writing PrettyDiff. * https://github.com/prettydiff/prettydiff

> Ideally, I think I'd like to have [comments] deemphasised by moving them off to the margin or something like that This is one reason I'm a fan of Douglas Crockford's slightly unorthodox style of always beginning comments in column 0, rather than indenting them along with the code. This helps, to a small extent, in differentiating comments from code. Example: https://github.com/douglascrockford/JSLint/blob/master/jslin...

Ignoring the fact this discussion about this, and this culture as a whole, is a minefield to navigate, it's important to note that Douglas Crockford can definitely be abrasive [1]. The issue at hand is that whether this abrasiveness is a bad thing, when compared to the contributions he's made and whether it leads to constructive discussions. The javascript developer who took offense (Kas?) definitely seems to have taken it too far, automatically associating Douglas's personality with being a jerk. The other issue at hand is how this influences tech conferences, because I've always attended conferences with the implicit assumption that I was there to learn first and foremost. Discourse and disagreement with speakers is natural and should be encouraged, as it oftentimes leads to enlightening discussions for bystanders and conference attende

see JSLINT license ( https://github.com/douglascrockford/JSLint/blob/master/jslin... "The Software shall be used for Good, not Evil." ) Only one documented exceptions : Douglas Crockford “I give permission for IBM, its customers, partners, and minions, to use JSLint for evil.” http://dev.hasenj.org/post/3272592502/ibm-and-its-minions More info - see HN archivum : JSLINT + EVIL https://hn.algolia.com/?query=jslint%20evil&sort=byPopularit...

You will probably get hundreds of comments with unsolocited advice, but let me just say to checkout and setup JSLint: https://github.com/douglascrockford/JSLint Setup and how you use it is more important than just using it. I run it in three places: 1) In my IDE (bound in vim on save, same in TextMate) 2) As a Git checking hook 3) In deployment / build scripts Turn all the warnings way up and it always catches redeclaration bugs. Set it up once and don't allow any code to get checked in or deployed with even a single warning present. I also pass all Javascript through the Google Closure Compiler, but with the lowest compilation setting, because it is very good at picking up small errors as well. (if anybody is interested in how to set this all up I can publish my configs and scripts)

Crockford's code style is very peculiar: https://github.com/douglascrockford/JSLint/blob/master/jslin... (I really hope that this is not coding-style-of-the-future) As you can see single Object.create callsite becomes a construction site for objects that might _not_ share a common structure (they potentially have different prototypes).

Here is the source: https://github.com/douglascrockford/JSLint