5 ms·
And (this might be obvious), but read, read, read! That's what works for me at least. Articles, books, blogs, IRC, IRC chat logs, Github issues, etc. When I am
by WorldWideWayne 11y ago
And (this might be obvious), but read, read, read! That's what works for me at least. Articles, books, blogs, IRC, IRC chat logs, Github issues, etc. When I am learning something new I might spend a few days (or even weeks depending on the subject) reading around about it before I take that first step to build my side project.
- marcos123 11y agoMy brain works the opposite way, so I would caution against this. I don't truly learn until I actually start doing.
- philjr 11y agoIn my experience you need to do both!
- newton10471 11y agoReading to learn is not borne out by research as a good way to build and retain skills, and can just as likely create illusions of competence http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect. Research shows it's far better to just start doing the activity. The reading should just be used to get you just to the point where you can start doing.
- WorldWideWayne 11y agoUnderstanding fundamentals before doing some activity is empirically more efficient though. Both thinking and doing are necessary for understanding the fundamentals of a given skill. Reading or communicating about things is a subset of thinking about them. It's all necessary at some point, whether you do it before, during or after your activity. I read to understand fundamentals and to get useful information such as which libraries, techniques, etc are popular in the arena that I'm entering or things to avoid. Many, many times reading has saved me from entering a given arena because I was able to conclude that whatever new technology I was looking into wasn't really going to work the way that I wanted.