> Language flexibility doesn't obscure the readability of code. I don't find it shocking, I think it's a sign of immaturity. > If you find that shocking you would probably drop dead at seeing what Lisp programmers get up to with macros :) Make new empty object, stuff with properties of all argument objects, season to taste, return. But if objects are effectively just bags of properties (a.k.a. Oh, and one problem with this prototype business is that in fact it is single inheritance (in the typical incarnations, at least am I invoking a strawman)? It seems inescapable that supporting multiple inheritance under the prototype paradigm requires that we make a single new object out of two or more existing objects. (That is also designed that way in order to pander to implementation ease and certain run-time efficiencies but has been turned into fallacious arguments like 'multiple inheritance is bad. Java has single inheritance, which sucks but it has multiple inheritance of interfaces at least, and good luck doing any serious work in Java without that being involved. By inheriting from foo, I'm enforcing the decision that this cannot be a bar, which could cause a problem to a future maintainer (maybe myself in six months). It bugs me even if there is no plan to do that in the current program. Like, okay, we got the properties of foo so that means we now absolutely cannot be a bar. I hate being locked to single inheritance. I still like its expressiveness and power, but if it becomes another C++ in future, I have to look somewhere else. When I look at the amount of features added to the language specification, sometimes it seems like it is going to become another incarnation of the C++ specification. (The most famous of these might be typeof null = 'object') Still, there are some (many?) edge/corner cases and unfixable bugs (aka features) that the language is stuck with for the sake of backwards compatibility and developers have to learn these.

you have great metaprogramming capabilities that make this language much powerful. Then I learnt that prototypal inheritance is a superset of ''class''ical inheritance as well as this. The prototypal inheritence and 'this' were confusing to me and took much time to understand those. JavaScript is very expressive and powerful language. Just another side of the coin, I suppose. I don't think that just those really give you the full picture that you need though if you actually want to build professional web applications. Obviously, the React and Redux documentation have been great as well. Eloquent Javascript 3rd Edition - Book being discussed, really enjoying working through it. Mozilla HTML Reference - Can't get any better than this documentationĤ. Learn CSS Layout - A nice write up for understanding what CSS actually is doingģ. Fullstack React: The Complete Guide - a wonderful book with a bunch of practical applications to buildĢ. I've been working through the following resources with a decent amount of success I think:ġ. I'm still learning, but I've found that just the official documentation doesn't quite get you there if you want to get the full picture. With little javascript/html/css knowledge, I used a couple different resources. But just from my perspective, I've been a backend engineer for most of my professional career and wanted to pick up front end dev. I also have a bit more time now that I'm stuck at home on evenings and weekends. I'm not competing with the experts out there, I just want to learn new skills and build things that I couldn't before. It's very likely that I won't finish everything on my list this month, due to other obligations, but that's ok. I have experience with Javascript and VueJS from a couple of years ago, so my goal is to catch up with modern JS (ES6+), brush up my JS core knowledge (not just frameworks) and learn ReactJS. Learning new languages, frameworks and building side projects helps me through the low periods and enables me to work more fluently with developers. My measure of success is being able to understand development at a lower-level. I just break my learning goals down into small, manageable tasks and revise as needed.

I'm not a 10x developer, so I don't measure myself against 10x tech bloggers or other 'experts'. It just depends on how you look at things and how you measure success.

I get burned out at work multiple times each year (I do mostly technical writing, training, and support). Definitely don't get down on yourself-going through periods of low- and high-productivity is normal.

Javascript eloquent