I think the standard ones are: Blog CMS Store But I think it's important that you will work on something you are passionate about.

I agree with some of the things Mark said: I do care about working with brilliant people, have a stable job with a good salary and I wish I will be able to work remotely. But if I can pick only 2 out of those, I will definitely pick stable job (work at the same company till retirement) and working remotely.

I love JavaScript, I get to do all the front end in JS. However, before I moved to front end I did a lot of IT and Infrastructure management. I got to write many scripts in Python and also implemented a back end to monitor and manage services in my previous company. Python is my favorite programming language because it is easy to write system programs that work without dealing with thinking of how to do it. Nevertheless, I am not really going to recommend on it for any projects. I believe type checking is very essential when working on big projects and there are good programming languages that give features that you don't have in Python or aren't trivial. Probably, my next programming language will be Go or Elixir. I heard many stories and good feedback on them.

Can you copy all your components code lines because it's not clear to me how exactly your code looks like and what might cause the problem. However, what I think the problem is how you control or save the state of your component. I wrote an example of how I would do that. Feel free to let me know if that's what you meant or I am missing something. https://codesandbox.io/s/0pmkyy0jmw In addition, I believe e.stopPropagation() stops the event to bubble up in the chain but once you change the state the components that are listening to that state will be rendered. Thus, I think the problem is how you handle or structure your state.

I agree! Software design questions probably make more sense than these algebra/brain-teaser problems. Thanks. :D

Thanks Gabor! That's so nice of you to say. :)

Oh my! I would get a conniption if they asked me that! I'm glad to hear other people share the same feeling as I do. I mean, I wish no one would felt that way but if that's how it is then at least we all feel that these interview questions are not easy. Thanks for your comment.

I didn't use vagrant that much so take my answer with grain of salt. From my experience, I had to write a command line inside the vagrant file that specifies bash commands how to setup, run and install my application. At the beginning I used it to run my application in an environment that is similar to production but comparing to Docker this is an overkill because I don't really need to install a big image of the operating system and the resources that the vagrant box took was high and I had a i3 core laptop with 6 GB RAM which means it slowed my laptop really bad. Vagrant.configure("2") do |config| $script = <<-SCRIPT dnf install nodejs npm cd /app npm install npm run serve SCRIPT config.vm.synced_folder "Users/smkd/Projects/my-react-app" , "/app" config.vm.box = "fedora/26-cloud-base" config.ssh.forward_x11 = true config.vm.provider :libvirt do | domain | domain .cpus = 4 domain . memory = 30000 end config.vm.provision "shell" , inline: $script, privileged: true end In my current job we are using Docker. I am running it on Linux so I don't know how it is going to be on Windows or on MacOS because I heard that the user experience is different among them. I am really happy with that choice. In Docker the image files are smaller and to setup the environment is very easy. I am sharing my code folder with the container environment although I had to tweak Dockerfile a little bit to set uid and gid to my Linux desktop otherwise it will run it as root and cause file permissions problems. Anyway, I recommend on Docker.