I've got a bad feeling about this. Maybe it's just me but, personally, I think Microsoft has a bad habit of overthinking and overcomplicating what should normally be the most simple of processes. My worry is that they will do the same with Github. I really--REALLY--hope I'm wrong.

Assuming you're a freelance developer, it really all depends on the project you're working on and the expected final outcomes of the project. When I first started diving into frameworks the biggest mistakes I made were not understanding the environment I was working in and not taking the time to learn the platforms that were already in place . Unless the client has explicitly told you otherwise or this is a brand new project with nothing to build off of , they'll often want you to build off of the already existing foundation instead of throwing out everything and starting from scratch. Know the Environment The quickest way to determine which tools you'll need to utilize for any given project depends on the following questions: What computing platform does the client primarily operate on? What web browser does the client primarily use? Is this project meant to be used internally or will it be used by the public at-large? If you're unsure of the first two questions, this website is a great resource to get a good idea of the the environment you'll more than likely encounter. The last question can only be answered by the client. Know the Pre-Existing Platforms In-Place (If Any) If the client already has a platform that they prefer and want to keep, then it's up to you to learn how the platform operates and its API. If, however, this is a brand new project, a good idea of which platforms are the most popular for their specific task can be found using BuiltWith . It's important to realize that certain platforms and libraries are developed for specific purposes involving certain types of data. Whichever framework(s) you end up using, just make sure you're using the right framework for the right environment.

The last line in your post said it all! 🙌 I couldn't agree more!

var users = [ 1 , 1 , 4 , 4 , 5 ]; _ .uni q( users ) ; console. log (users); // [ 1 , 4 , 5 ] Lodash makes it really easy to fix duplicates inside arrays. I use a custom-build version and _.uniq is one of my core-essentials.

Hi everyone-- My name's Davey and I am the web dev and sys. admin for one of the Team USA Olympic sports where oversee 13 websites. Prior to that I was a freelance IT guy just fixing computers out of a garage. I first started coding when I was 15 but have been playing with computers since forever. I remember learning DOS on my dad's old IBM just because I wanted to play the golf game he had installed. My dev-environment-vices are usually... Mac-native Apache Mac-native PHP Homebrew for some things NPM for others MariaDB Multitail is a MUST HAVE Node.js Gulp Foundation Sublime Text 3 Querious is a MUST HAVE I'm always on the lookout for a solid, lightweight framework that lives by the credo, "Less is more." It's those frameworks that ultimately shape my thought process when writing any/all lines of code. When I'm not coding you can almost always find me engulfed in my other passion: Rugby🏉 . Yes, I am an American and I refuse to watch the NFL and (pretty much) any/all American sports. They are just too boring for me. My sport interests are found overseas, mainly... Rugby Union Aussie Rules Footy NRL BigBash Cricket If anyone has any questions or needs any advice on things, please feel free to ask. I'll always make it a point to help anyone in anyway that I can. Cheers🍻

Some of these are really just a matter of personal preference. Results may vary but here are mine: Sublime Text Editor Node.js - Had it not been for Node I'd still probably be using CodeKit! NPMJS Github Underscores.me - A true plain WordPress boilerplate template. Foundation Site Docs FoundationPress - A WordPress template w/ Foundation already integrated; This was the repo the ultimately lead me away from CodeKit and permanently into Node. For Mac users: Perfect Web Development Environment JavaScript Modules: A Beginner's Guide Part I & Part II LESS2CSS - Preview the final LESS to CSS output side-by-side. CSS Guidelines - High-level advice and guidelines for writing sane, manageable, scalable CSS. SQLFiddle - Like JSFiddle but for queries. Browser IDE's: JSFiddle.net • CodePen.io • FiddleSalad.com • Feditor Documentation: DevDocs.io • DevTools For Pure CSS: UserStyles.org For those of us who remember the old UserScripts(dot)org : GreasyFork .org

Due to being a one man web team for an Olympic sport, I don't really "support" IE 11 but I do have a landing page explaining that our website is not compatible with Internet Explorer and provide multiple links on where users can download a modern web browser. That still doesn't stop a few individuals sending messages professing their undying love of IE and state that they're just going to stop following us. My response to them is, "Okay."