I like the idea but I think this challenge is more for design-oriented people. Most of the people following Hashnode tend to be development oriented. I like the initiative but I hope next time we could get more of a dev problem to solve.

Just create another account and shift your repo there. If it is your employment you are concerned about, you gotta bend the knee here coz one way or the other, someone will taste bad blood in the end. Who the fuck asks for GitHub password? Who the fuck asks for any password? And if they are such geniuses, they should have blacklisted Github.com in their firewall when they had the chance and used and enterprise self-hosted Github server of their own to keep the company code. Boi, you are working with idiots I am telling you.

Hahaha.. My education system did it for me. Welcome to India.

Reading is knowledge, practicing is wisdom. You must have heard of people who had little knowledge but had a lot of wisdom because they kept practicing what little they knew and started learning as and when required. What practice gives you is experience and a much-needed skill of pattern recognition. Experience helps you learn from mistakes that reading can't teach you, and pattern recognition helps you save time, this again, cannot be learned from a book. So I believe in reading when required.

I do it like this: If I have no clue about the topic, I either watch a video in which the persons build something really simple with it. Or I usually read a blog post in which the guy builds something. I usually tend to code along with the blog post. Coding along the video is distracting and hard to accomplish. Once I am comfortable and have a birds-eye view of what that thing really is, I start reading books or more elaborate resources. Learn from the master, doing things the hard way is actually the right way doing things and learning a thing or two in the process. Jason Knight might give you a great insight into this.

The point of using redux is to minimize the use of scattered component states in your app. Redux maintains a single state for your whole app and it would be best to keep it that way. The key point is: If the view needs to re-render when the data changes, store it in the state ( Preferable the redux store/ app state ) else don't. In your case, it seems that the data does not change once the component has been rendered, hence the use of state shall not be required.

Go for Dell XPS 13. It is a brilliant laptop with a great screen. Plus you have the plain old keyboard, just the way you like it. Also, it can handle all you web dev stuff. Unless you are planning to do ML training on it, it should be good. It is a premium laptop though, so it is a bit costly. But you won't regret the investment.

Have you heard of powerLevel9k or oh-my-zsh? This kind of functionality already exists. But you can pat yourself for the hard work you have put in. Good job.

The first function will by default return the value of console.log(a) which happens to be undefined in this case. Had it been some function that returns some value, you would have seen fn1 return its value. In the second function, it simply executes the code inside { } and would not return anything until you explicitly use the return keyword.

I have been using LG 22MP68VQ for quite sometime and I must say I am pretty much satisfied with it. It has that infinity edge kind of display with very thin bezels so it has a modern feel to it when you see your code on it. Sharp and crisp images are its specialty and 22'' is more than you can ask for.