I was originally going to make a post about continuously seeking and pushing the boundaries of your knowledge.
Aside from already having done that, like, two times already, there’s something much more important here. You need to know when not to spend the time learning something new. I’m leaving entirely new subjects aside, because those first few steps always have a high chance of being long and painful, but what about subjects you already know a bunch about? It’s always good to get broader knowledge within a field, but it may not always be worth your time.
I wanted to contribute to a section of Urbit I had never touched before today. It’s wildly different from the stuff I had fumbled around with already, but also an important part of the project’s core. I looked the section over, scratched my head. “Hey, is there any documentation for this?” There was. A single, ten-thousand-word page explaining it more or less from the bottom up. Basically the complete opposite of what my preferred learning method requires.
Some time was spent reading through bits of that documentation, and some things started making sense. Cross-referencing with existing code didn’t tell me anything though, it was still all rather confusing. I could continue to study up, and I’d eventually get it, but that’d take an enormous chunk out of my time. Time I could spend much more productively contributing to other parts of the codebase, or writing tutorials (of which I finished a 3.7k words part today, hot damn).
Yeah, I’d much rather get more productivity for my time here.