The problem with this article is that most of the innovations that browsers are now bundling came from the community, in the form of libraries or frameworks. (document.querySelector, js templating, promises, observables, server push, etc)
Libraries & frameworks are the way new paradigms are explored and improved. They are not the future, but they contain the future.
Also, fitness advice I can trust and nutrition plans that work? Why should I trust you guys over anyone who has an actual background in exercise physiology or nutrition? Do you have any evidence that your nutrition plans are better than premade ones online? I'm blown away that people give Soylent so much crap, but they're following the same principles as apps like this (an "if it fits your macros" approach) but do it with consistency and accuracy that a meal plan could never achieve.
It looks like you're off to a strong start, and I wish you the best of luck, but the app so far looks like it's strongly overselling/under-delivering which can be pretty offputting.
It's really not a matter of whether or not you have a gym membership, it's a matter of the actual exercise you do. You can have a gym membership but if you spend your time doing the wrong things you won't get the results you're after. I myself go to the gym, as well as performing bodyweight exercises. They're clearly different, and we're not suggesting otherwise. However the bodyweight exercises are often more convenient for people with busy schedules, or who travel a lot.
As for the nutritional aspect, we're not inventing anything new, and we don't have any magic formulas. We're just helping people improve their health understanding the effects of the things they eat. It's not a fashionable diet, and it's not rocket science. It's pretty much standard healthy living.
The conclusions drawn are a rich work of imagination, when not patently false.
I say this a front-end developer who has to write HTML, CSS and JavaScript on a daily basis. Yes, strictly speaking, HTML and CSS may be considered programming languages, but they lack control structures, design patterns and other interesting tenants of computer science. Like the author, I'm much more drawn toward the CS-related tasks of the job such as writing JavaScript.
To be clear, I have an enormous amount of respect for people who enjoy the design aspects. Writing CSS, using Photoshop, etc., requires a lot of skill. My point is simply that there is a divide among those front-end developers who are drawn toward programming and those who are drawn toward layout and design.
As more sites gravitate toward complex JavaScript-driven web apps, it may be useful to ditch the general term "front-end," differentiating C.S.-oriented front-end developers from those who prefer visual design.
This might make the expectations of a front-end development position much clearer, allowing for a simpler interview process.
If you've never really enjoyed your job I can't fathom how it's taken you so long to realise this isn't for you.
Wait, is this ironic?
No, it's just unintentionally hilarious. Damn you Alanis Morrisset. An entire generation misuses that term because of you.