robinrheem
Joined 7 years ago
Joined 7 years ago
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.
PS. Good luck with the blog! Hope I get to read your entries some day :)
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"?