first id like to say that this is my option and that im not always 100% correct. I looked around a bit and managed to find the original 10 page memo https://www.documentcloud.org/documents/3914586-Googles-Ideological-Echo-Chamber.html (here for the pdf https://assets.documentcloud.org/documents/3914586/Googles-Ideological-Echo-Chamber.pdf) and frankly i dont see anything wrong with it, while i do disagree with most of it i dont think that he should have been fired over it. and i definitely would not call it an "Anti-Diversity Manifesto". in fact in multiple places he goes out of his way to state I strongly believe in gender and racial diversity, and I think we should strive for more page 6 either way, id say read over it and draw you own conclusions :D

thanks for the kind words. :) as far as what I would recommend learning. I would say dont forget about some of the "older" technologies and libraries. while React, Mongo and Express are cool. definitely try to become familiar with libraries like, AngularJS 1 and Jquery. because chance are you when you do find a job, they will still be using "older" libraries. and it will help to be familiar enough with them enough to not be completely lost.

I don't want to sound like i'm bragging here. but i'm 19 and I have a full-time front-end developer position. although a few years back I was in the same situation you are in. I started learning web technologies a few years ago when i was about 16 - 17, at the time i could not get enough of it, I read everything that I could get my hands on. after high-school, I knew JavaScript / HTML / CSS front to back, and was considering skipping collage and going into the work force. At first searching for a job was hard, and my lack of experience in the field did not help at all. I worked with a lot of recruiters, although i never really got any decent offers, and the few offers I did get were for position not even related to web development. After about a year of searching I decided to start attending some of the local developer meetups in my city. it was awesome to talk to like minded people about things I was interested in. although more importantly I was able to build up connections. I did this for few months, and then at one of the meetups I met my future boss. we got talking about various technologies, and he mentioned they where hiring and that I should check them out. I did and that is where i am now :) I realize that I am very lucky to have gotten such a good job so early on. although I wanted to point out that it is possible if you keep at it, and don't stop learning. good luck :D and if you have not done so already i definitely recommend checking out some of your local dev meetups.

IMHO computer cant answer questions that we dont already know the answer to. for example, the reason computers can land a rover on mars is because a lot a really smart people thought it how to. essentially computers cant teach us anything until we first find a way for a computer to learn on its own, which might prove to be hard. again just my opinion. and im in no way an expert in this field :)

my bad. :D although some of my point still apply to service workers. they are similar to web workers but with a ton more functionality and features :)

they are pretty much like opening another browser tab that only runs JavaScript. they also have some different APIs for sending messages back to the parent window. as far as what they are useful for, well a lot of things, but one of the most common uses for them it to process a lot of data without freezing the current browser tab. since they are technically a separate tab you could run a while(true){} loop in them and it would not crash the current tab.

considering that most of your code will be running in NodeJS i would recommend using ES6. while its absolutely possible to use typescript with node, i think the benefits it offers would be outweighed by the downsides of having to compile it, and having to use source maps when debugging. also node 6.5 onward supports 97% of ES6 features. https://kangax.github.io/compat-table/es6/#node6_5

id say a little of both. try solving it your way first, and after you have failed a few times, go check out the ways that other people have solved the problem.

very well said "pick your battles, focus on your current pains"

thank you for taking the time to answer my question your the type of person that makes this site so awesome :)