Command line stuff is fun, I really enjoy experimenting with that. Using JavaScript in different use cases, like browser internals and TVs and alternative devices is fun. Sometimes I play around with PHP if I'm bored. These days it's more about application/use case than languages.

1. Unfortunately I don't have much Windows + Node experience but I haven't heard of any issues so I think you're probably safe

2. Grab a Heroku account and deploy away!

3. O'Reilly has a book for everything. And always code something you have a real use case for -- it's the best way to learn!

I have a beautiful wife and two rambunctious little boys I spend most of my time with. I sometimes sneak away to pwn n00bs at whatever the latest Call of Duty game is. I'm obsessed with soccer so I watch Arsenal, Real Madrid, Dortmund, and any other game that's available. I also love a glass of wine or a beer with my wife when the kids go to bed!

1. I trust O'Reilly books the most; they tend to get the best authors and those authors oftentimes speak at O'Reilly conferences. Any of the advanced JavaScript books (client side and Node.js) usually catch my eye!

2. Chris Coyier, Eric Meyer, Alex Russell, Lea Verou, and many, many others!

My blog takes up the majority of my free time so I don't have many side projects. Luckily Mozilla encourages us to contribute to other projects so I've been experimenting with the Mozilla Tofino experimental browser, as well as Dev Tools and a few other Mozilla projects!

CanIUse says that flexbox is in all modern browsers so if you want to use it you can. I'm more reserved in my CSS structuring and have seen plenty of odd flexbox bugs so I'm not ready to use it yet, at least not for an entire complex site.

Get away from the computer! Burn out happens a lot when you work from home because work is a moment away. I'll take the dog for a walk, break to` watch a TV show with my wife, or go for a quick drive.

For those of you who work in an office: make yourself leave on your lunch break, don't eat at the computer. At the very least go for a drive. When you walk outside and you see trees and grass and people doing things other than punching keys, you'll remember that life is more than work!

The best way to join any community is by contributing! Contribute to enough Mozilla projects and with a great level of quality and you'll be a Mozillian in no time!

Funny fact: when I joined the MDN team, there were 5 other people and none of them had a CS degree!

Here are a few tips I always share:

• Write in your own voice and in your own conversational style.
• Make yourself publish on a regular interval
• Write about whatever comes to your mind; forcing yourself to write about a given topic all the time will drive you crazy!

Hope this helps!

Open the JavaScript console and start experimenting! I also recommend downloading the source code of popular open source projects, like jQuery or MooTools or React, and try to understand what they're doing. There's nothing better than looking at a working product and seeing how they're doing it! And read blogs! (hopefully mine!)

I know it's been popular for a few years but I'm still incredibly excited by Node.js . I'm also excited about Electron and some of the stuff Mozilla is doing, like Tofino. React is being used in Mozilla's Dev Tools and Tofino, so I'm exciting about that as well. I had a blast working on Firefox OS for TV -- I'm super into alternative use cases for JavaScript. In short, there's too much out there to keep up!

Through my blog! Mozilla's head of Web Development at the time saw my blog, followed me for a while, and thought I would be a good fit at Mozilla. And I hopefully have been! :) Mozilla has changed my life! I get to travel and be around the best developers in the world. What more can I ask for?! :)

I was on the MooTools team so I'm obviously partial to that. I worked at SitePen for 2 years so I was very well acquainted with the Dojo Toolkit, which is amazing. Facebook hired much of the MooTools team who have worked on React so I recommend that. three.js is amazing for visualizations. There are too many awesome tools out there right now!

Nothing more than keep experimenting and keep plugging away! I spent thousands of hours teaching myself coding techniques and tools. 40 hours a week doesn't cut it!

I never look on S/O purposely but they have a hell of a SEO strategy because they often show up top of my Google searches. If I do find a gem on S/O I'll reference it in a new blog post, detailing my case for needing it and hopefully explaining it all better than S/O's limited context seems to allow.

WebAssembly will definitely be the path forward for games and very heavy JavaScript apps. Flux and redux are super popular so I look forward to working more with those. Of course no one solution will take over but what I do hope is that the base technology stays easy enough that kids (like I was) could teach themselves how to publish on the web!

The truth about working from home is you can either handle it or you can't. I've heard dozens of people tell their stories of being fired within a month or two because they weren't getting anything done because home felt like leisure.

I've never had any problems working from home because it fits my goals for a work environment: quiet, very few interruptions (imagine how many people stop by your desk at a traditional job), no one looking over your shoulder, comfortable, etc.

My typical day is 9-5 because I want to hang out with my family before my young kid goes to bed. Most communication is over email and IRC but big decisions are made via video meetings. Every once in a while I jump into a video meeting with colleagues just to "hang out".

Sometimes I work outside, sometimes I'm in my office, sometimes I'm in my living room with soccer on. All depends!

• MacBook Pro
• Atom text editor
• Docker
• IRCCloud
• TweetDeck
• Every browser you can think of
• 60" Ultra HD Panasonic TV
• Various other command line apps!

THANX MAN

Travis CI, AWS for a big project, git, Node.js, and whatever front-end JS components the specific project needs. I try not to be too rigid though -- if a project is best using a different stack component, I'll go for that!

1. I love JSX -- I hate jumping back and forth between files to see what I'm templating into.

2. My strategy has always been to take a use case that I'd need and learn the new language using that case. For example, when I first taught myself PHP waaaay back in the day, I created a PHP app to catalog all of my DVDs. I could do basic CRUD, sort by actor or run time, etc. So within a few weeks I learned PHP and MySQL, and I was driven to keep going because I wanted a DVD app! :)

Unfortunately not; I spent 3.5 years on MDN, 6 months on services workers, and now I'm working on version control tools. I try to dabble in other projects on my free time!

Never go for the cheapest option, always opt for tools that offer support from your native country, always ask for input from the users, and don't sign long term contracts!

1. As someone that codes 95% on the client side and with async structures, converting that ideology to the server side hasn't been too difficult. I guess I'd say the best philosophy to have is to never assume successful routine execution.

2. Not really; I usually try to "code to make it work", then "refactor to make it pretty". This philosophy allows me to keep my line of thought without thinking too much about minutia.

3. It really depends on the project and, to be honest, I usually just defer to others on the team. I do like BEM methodology though!

Not really; I'm a "make it work" first, "make it pretty" second type of guy. So I'll make sometime work then conform the code to the specific project!

Absolutely! Here are a few tips I always share:

1. Write in your own voice and in your own conversational style.
2. Make yourself publish on a regular interval
3. Write about whatever comes to your mind; forcing yourself to write about a given topic all the time will drive you crazy!

Hope this helps!