[tumbling_stone]

Exactly. I had been wondering if my way of sticking to work related things while exploring stuff in my own time was the best way of learning, but due to the kind of free time I get it is the most optimal strategy. For example though I would love to complete SICP I just don't have the kind of time it needs, so instead I try to read as much as possible about OOPS explore languages that are exemplify OO design but aren't that mainstream like Pharo. This way I don't have to worry much if the knowledge acquired would be forgotten and wasted, whatever I learn I practice at least a part of it daily.

[hellofunk]

I'd offer a different take. SICP is pretty intense stuff in parts. Don't feel obligated to understand it all or to finish it as a full-read. Rather, when it gets tough, continue reading, but give yourself permission to not fully understand it. Skim it, whatever, the exposure will leave something. You can always come back for a second round. But, more importantly, also explore many different programming paradigms, don't just focus on OOP. Learn a lot about FP, FRP, Declarative. Whatever paradigm you use, it will make you think more openly about problems.