Check out this post on Cheng's blog . The author did a very good job answering these questions.

You can use media queries and set the font-size attribute on the html element (using px ), and then set the font-size of other elements using rem , like so: @ media screen and (max-width: 720px ){ /* smartphones breakpoint */ html { font-size : 12px } } @ media screen and (min-width: 720px ) and (max-width: 1024px ){ /* tablets */ html { font-size : 14px } } @ media screen and (min-width: 1024px ){ /* laptops */ html { font-size : 16px } } h1 { font-size : 2rem } Obviously, you can add/modify as many breakpoints as you want. This will allow you to make sure you control what is happening in edge cases (as always, you should test your work using the Chrome device emulator feature, or real devices if possible). Mixing this technique with the one suggested by Chris Stephens could also be interesting. For example, you could have an an upper & lower breakpoints with absolute font-sizes, and relative ones in between. Hope this helps :)

Hashnode ? (I know, too easy)

Yes, sure, but I am not sure that this explains the 39KB addition :p (or maybe they wrote the name of every team member in the source code).

git reflog can save lives. Sometimes. It's useful when something goes wrong when you commit, and it does not appear in your commit log.

You should take a look at taiga . It features Kanban & Scrum boards, backlogs, comments, integrations with VCS and other services via web hooks. To me, it's a very good alternative to JIRA with less functionalities, but a much cleaner UI. Did I mention it's open sourced, free for public projects (you can have a private project for free if you want to try it) ? Plus, it's updated quite frequently based on user feedback. I was very satisfied with it when we used it in my team (4 people).

@michaelgilley Perfect answer ! I voted for Classes, but with the same reservations :) There are many interesting articles on this subject such as ES6 classes and JavaScript prototypes . A good way to understand this in my opinion is to use babel's REPL to see what ES6 classes actually translate to in ES5.

The answers provided in this thread are a great start ! You can also checkout A visual guide to CSS 3 Flexbox properties by Dimitri Stojanov, I think he did a great job explaining how each property works ! Once you get your head around the concepts, I think you'll fall in love ;)

Hello Joshua, I have used Ionic in my previous company, in a fairly big project. Now that v1.0 is out, I think it is really stable. Plus, the devs behind it are really reactive, and the community is great. I think the project' size might not be so important, compared to the need for native features, which will require additional (and OS specific) plugins. With the team, we found that if we did not need too much plugins, and did essentially CRUD operations, Ionic was the perfect fit, with the added bonus of not having to write a single line of code specific to a certain OS. However, if you have to use many plugins, it can become a bit messy. Of course, there are more & more great Cordova plugins everyday but still, we faced issues. So always, "it depends" on your project, your team' skills, but one thing I can guarantee, is that Ionic is fun to learn & work with. Hope that helps !