The younger more unstable brother of Sublime Text 2. I use this even though it’s still in beta because it allows JSGutter to run Node.js and jshint my code in real time instead of just on every save or load.
I used Webstorm in a project in my previous job, and I’m not sure whether it was my laptop being substandard or Webstorm being a resource hungry beast but it was slow and sluggish for a JS IDE. But, fast forward a year, I’m not sure if it got more efficient or my machine upgrades provide it with the juice it needs but WHOAAA! I’m running it on both Fedora 20 and OSX with i5 and i7 processors and 16Gb ram in each, it’s the tool I was expecting it to be. Fast, great linting, unmatched intellisense. It’s a great product. Sometimes you can get the feeling it’s got too much on screen but it’s just a case of finding the configuration that works for you. It is loaded with keyboard shortcuts so my advice is to print out a Webstorm cheatsheet and tack it to the wall beside your screen. When you start storing them in muscle memory, you’ll barely even need a mouse in your life! Check out the 30 day trial!
Exactly the same idea as JSFiddle except I like the fact that it live reloads so you don’t have to click a run button each time. Just write your JS and watch your logs appear in the console or output window
I’ve just started listening to this podcast and they seem to have a ton of interesting topics of discussion. Worth checking out.
My teammate at CAM tech just told me about these podcasts, apparently NodeUp is an already established podcast and they’re starting a NodeDown for the Southern Hemisphere. I’ll be checking these out. You should too!
MongoDb meetup is one I attend when I can. We use MongoDb in our side project so it’s interesting to listen to case studies and experts talk about it. Also, Stennie (@stennie) and the rest of the Mongo crew are super friendly and always willing to help out if you have any issues with your Mongo implementation.
This is actually a book written about Java but I constantly refer to it no matter what language I write in which is why I’m including it in my list. It takes you through examples of bad code and explains why they are bad and how to make them better by transforming them into great looking, readable code. Because after all, 99% of the time, you’re not writing code for you too look at, you’re writing code which other people need to be able to maintain with ease.