I do tell myself to just "study enough to produce" but I just can't get the right criteria for "enough".
I wonder whether this type of behavior is called anything so I could study about it.
1–10 of 25 posts
I do tell myself to just "study enough to produce" but I just can't get the right criteria for "enough".
I wonder whether this type of behavior is called anything so I could study about it.
You might also call it research.
Consider putting your studies together as blog posts or videos so that your research becomes art in its own right. "Process is art".
Might call it analysis paralysis. You might also call it research. Consider putting your studies together as blog posts or videos so that your research becomes art in its own right. "Process is art".
My 2 cents: Learn by need. Figure out your needs (e.g. required feature) and go get just that knowledge from the internet, and put it to practice.
I've always just called it "rabbit holing" and I'm guilty of having a problem with this as well. That said, I do still manage to get stuff done, so clearly I manage to break out of the recursive rabbit hole process at some point. What I can't do is tell you that I have any kind of definite / deterministic / repeatable process for managing this tendency. I usually just reach a point where I'm like "OK, enough is enoug…
I did an experiment on myself where I just design a project and start implementing it right away without any research. When I get trapped, I just did a quick Google search and solved the problem right away instead of trying to study about other solutions or other variables about the problem. I got the project done rather quickly but code quality, solutions that came from the top of my head weren't that impressive. I know iterating will enhance quality, but before I iterate I need to study better solutions or at least research to get ideas for better solutions in order to iterate.
The result of that experiment was just that I was able to get things done a bit quicker if I just did things without studying and only "find solutions" when I encounter problems. Going deeper needs knowledge, but when to start building again when I acquire "enough"?
Exploration vs Exploitation in ML. It seems you explore a lot to find whats 'best', but it keeps you from implementing (in this case Exploiting) a set of ideas. There is an optimum between the two. You could read up on this. My 2 cents: Learn by need. Figure out your needs (e.g. required feature) and go get just that knowledge from the internet, and put it to practice.
For almost 2 years I have had some art projects that involve doing something every day so that gets me learning gradually.
I want to start blogging again though to write up what I've been doing and when I start setting up a 2022-technology blog system I find myself getting stuck in the weeds (this Hugo template example looks good but put some real text in there and there is just no room...) or generally dissatisfied (like Hugo is great for anything that doesn't involve art or math except that's what I'm writing about.)
I'm not going to be happy blogging unless I can understand the whole graphic design system and I just haven't gotten my head around it but writing about my art project just now I start thinking I'm going to have to attack CSS the same way I attacked printing.
It depends on what I am doing. For almost 2 years I have had some art projects that involve doing something every day so that gets me learning gradually. I want to start blogging again though to write up what I've been doing and when I start setting up a 2022-technology blog system I find myself getting stuck in the weeds (this Hugo template example looks good but put some real text in there and there is just no room…
PS. Good luck with the blog! Hope I get to read your entries some day :)