I would focus on one of the big view players - React or Angular, from facebook and google. It seems like the old school jquery dom updates is out of fashion now. I wouldn't worry about the toolset, it sucks - webpack I guess has some uses.
I would focus on the core thing, e.g. React and javascript fundamentals. Tooling and stuff will follow along once you get a job in it.
I'm interested in using nodejs to replace bash scripting, I loathe doing any kind of logic in bash and I just want to excise it. No maven or gradle for build tools. I'll revisit later.
Good domain name as well, easy to memorize, good job.
to pick at the 1-2% numbers a bit the impact of IQ depends on the individual; physical size/height is only profoundly important for the success of certain people - athletes primarily. however, both also have correlation with success. I'm sure the paper was more careful than this article.
IQ is often used as a proxy for intelligence, when in fact it's just a set of standard metrics that nobody thinks is that good beyond a certain point - after all the term comes from early attempts to quantify developmental delay. Leaving that aside for a moment.
This only allows you to strangle yourself in a more CPU-efficient manner.
Locks et al. are low level interface, too low level for a language that pretends to be a high level one (like Java does).
> The other important point is that as soon as you get into working in a clustered environment, you start having to think about distributed locks and concurrency when there is not even a shared clock to rationalize things.
Once you go into clusters, you loose your precious notion of shared memory anyway (unless the distributed shared memory is still a thing; I haven't checked lately, but I thought it was an abandoned paradigm).
> So, for product oriented engineers, great go use nodejs and you can write JS on the front end and the back end and it will be absolutely tremendous
I don't know why are you implying that I either work on frontend, with web applications, or Node.js. I do none of these.
I thought you meant losing cycles due to blocking or spinlocks when you said strangling.
>Locks et al. are low level interface
Actually no, this is the world of multiple cores. Threads are the most trivially accessible way to parallelize activities, so they are just a modern primitive.
>Once you go into clusters, you loose your precious notion of shared memory anyway
Zookeeper. Distributed clocks and sequences and all that often require a few bits.
I was just making fun in the last sentence, if you didn't catch the linguistic joke about populism in my word choice. I'd guess you work in erlang.