Day 1 Jan 3:

What's 151 Days of Code?

1. I heard of this challenge on Tanay Pratap's discord server. The challenge is to write code for 1 hour daily for 151 days. Then either tweet about it or write a weekly blog post.
2. The challenge started on 1st Jan, but I am starting from 2nd Jan

Why am I taking part in it?

1. Right now I am in a position where I want to accrue as many skills as possible and to be decent at them. Aside from that I also want to clear the coding interview. To do both, I have to consistently do increasingly complex, projects and DSA problems.

How am I going to do it?

1. Track my time spent for the challenge and
2. Track the progress done in that time

Progress:

1. Setup local React environment and deploy a basic react app -> Local Setup Guide.
2. event from event.target.value is deprecated.

Day 2 Jan 4:

issues faced:

onchange not working:

1. MDN
2. The code above is working on MDN site but not locally.
3. Reasons:
   1. event must be passed as a parameter in the function

      input1.addEventListener('change', updateValue);
      function updateValue(e) {
       console.log("change detected");
       input2.hidden=false;
       btn.hidden=false;
      }
      

   2. give element.hidden = false; instead of giving element.hidden="false";

Progress:

1. Worked on making a cash-register app in VanillaJS.
2. Completed the functionality. Style improvement is left.

Day 3 Jan 5:

issues faced:

1. making the UI responsive. Although I tried, the UI may still break on some screens.

Progress:

1. Added style to cash register app
2. Fixed the reuse functionality => if the user interacts with the app again without reloading it first, it gives correct output now
3. Did some DSA coding

Day 4 Jan 6:

1. No coding
2. Read about clean code
3. Read about thinking and writing down what you are going to code before you jump to building

Day 5 Jan 7:

NamasteyJS - by Akshay Saini

Day 6 Jan 8:

NamasteyJS - by Akshay Saini

Day unknown

1. I wasn't consistent with the challenge but I surely did something in these days.
2. However, I am not content with my output.

Observations (Take these with a grain of salt):

1. When doing DSA questions for practice, don't give yourself unlimited time for any question. In any coding interview, they are not going to give you much time to think of an approach at the least. Open a question and start a 15 minute timer, within which to think of an approach to solve the problem and then start coding.
2. Do not start thinking of an optimized approach in the beginning. You might end up not solving the problem at all. Inefficient and working is better than Optimum and not working.
3. Having a basic knowledge of DS and algorithms saves time as compared to jumping into the question and learning on the spot (to each their own, but this seems true for me).
4. One should not focus on just DS or just Algos, when you're solving problems. You have to think in both terms, which DS would be best suited and which Algo would be more efficient.