torn trench
I am having some confusions about my works. Let me elaborate.
Imagine I am working on a software, basically a nextjs site. The thing is, whenever i am trying to build a page, I get stuck, and I feel like I do not have enough clarity about what I am going to do. To address this issue ,I created a spreadsheet containing all the features I am supposed to build, and added a column for status. Quite good, whatever does not exist on the spreadsheet, should not bother me.
But what is bothering me is, the microtasks. Such as, which API call should be made after which call, which function should be called, how should I organize the files, etc small things are bothering me. One solution I came up with is, create complete diagram about every little detail. I learned this from CP. Like, whenever we approach a problem, it is better to write the solution process in your notebook or something. And when you are comfortable with the solution entirely, then you start coding. The solution happens in your notebook, you just type it in the computer. I was thinking of something similar for my development works. But, it just adds too much friction and slows me down.
I wanted to know, the feeling that I have, is it actually a valid feeling or a random excuse my brain is coming up with for procrastinating?
Also, it is about watching code-along videos and tutorials. I often find it fascinating to watch other people building a nextjs project, react project or something. I feel like, watching these videos will give me a real feeling about how things work behind the scenes, and how good programmers write code.
But, as you know, these videos are generally over 5 hours long. I simply cannot afford that much time on watching videos. What is a better solution? Will I just learn to become a good programmer simply by working more, and connecting with good programmers or I should sometimes watch these typa videos too?
stoic mauve