[philomath_mn]

Hopefully this doesn't come across as too aggressive, but it seems like the other comments are pulling their punches.

There is a difference between

> I find myself studying too much in order to make something that I want

And

> So I start learning about the history of dashboards

The former is a classic problem in engineering, the latter is kinda nuts. If you are studying the history of something before building your first version, then you are almost certainly avoiding the work.

If you want to read up on the history as you build it, that is one thing. If you are going to build a company around dashboards and want a good first-principles strategy, then history might also fit in.

Otherwise, dive in, validate your idea, and make something work before you start reading about special topics, let alone the history.

[robinrheem]

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.