99% of the time I don't anymore. I used to read a lot, now I just pull information from the net, I have feeds of information exposing me to new ideas. Most tec

99% of the time I don't anymore. I used to read a lot, now I just pull information from the net, I have feeds of information exposing me to new ideas. Most technical frameworks have a ton of information readily available. The only books I go to are Math and Algorithm books I have on my bookshelf when I know something obscure I want is in them. Learning falls into two categories for me - Things you don't know you don't know - Thing you know you don't know I also learn things well when I do active experimentation. First one is the trickiest as you need ways to be exposed to something you don't know and being able to recognize its importance amoungst the flood of things you are exposed to. Things like HN are helpful. Second one I keep notes on things I know I don't know. These often are things that I kind of have a fuzzy idea of what it does, but haven't really spent time on understanding exactly what it is. For instance, webpack is on my list, I use it a lot, I modify configs and get stuff done. I have a fuzzy idea of how works. But I haven't spent any time understanding it from the ground up and don't know how to set something up from scratch. But at some point webpack will bubble to the top of my things where I have knowledge gaps. So when I work on my chosen knowledge gap, I read a bunch of things, conduct a bunch of experiements, look on stackoverflow and look to answer questions, see how other people have solved existing problems.