Not aggressive at all! I'm just grateful for your knowledge. It looks like procrastination but I don't have any intentions of avoiding work. I just like satisfying my curiosity. If I come to the dashboard example again, I want to know when it was made, how it was made, who made it, with what process. I don't like history books that just makes a story and facts. But I do want to know how Darwin got interested in species, what he wrote down in his journals, how he got to think about it, how he thought about it, etc. Same thing with the creator of dashboards.
To make it more precise, if I want to make something with Ruby on Rails for example, I tend to learn everything about Ruby on Rails. What kind of components it has, how the magic works, watch every video about its best practices, distilling everything. Then I find about DHH(creator of Ruby on Rails) and find how he built it in the first place. What thought process he had, what needs he had, how he got to build it, what he was thinking when he wrote the first version of Ruby on Rails, etc. Once I need a job processing library, I do that again.
If I were in your situation I would be studying about all the static site generators, onpremise self-served blog services, any type of new blog service that are good for writing about art and math. Okay, then what theme would be best? Survey them on each platform. What markup language would be best to write about art and math? Find about LaTeX, org-mode, Markdown, etc. I pretty much tend to do this kind of thing for anything I do!
PS. Good luck with the blog! Hope I get to read your entries some day :)
I did try to do the way as you said in your 2 cents but the more I solve problems like that I tend to feel empty. It feels that I don't know anything and I just know some exceptions or just some solutions to some problems. I don't feel I have a fundamental knowledge base that lets me think from my own neural networks.
Going too deep in the rabbit hole feels like procrastinating sometimes. I also do get stuff done but mostly when a hard deadline is set. So I tend to go into the rabbit hole until I only have a few days left. I also have good feelings since I love studying about things.
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"?
It's so nice to see these examples are increasing every now and then. Hope to learn a lot and I also would like to know about the use cases of nslookup dot io. One thing that's coming out of my head would be if I would ought to make a non-targeting crawler of some sort and not implement my own dns crawling infrastructure and just use nslookup.io and just cache the results.
To make it more precise, if I want to make something with Ruby on Rails for example, I tend to learn everything about Ruby on Rails. What kind of components it has, how the magic works, watch every video about its best practices, distilling everything. Then I find about DHH(creator of Ruby on Rails) and find how he built it in the first place. What thought process he had, what needs he had, how he got to build it, what he was thinking when he wrote the first version of Ruby on Rails, etc. Once I need a job processing library, I do that again.