fuzzygroup
Joined 14 years ago
Joined 14 years ago
1. Write a blog post about it. I'm an old school blogger and my best learning tool is to immediately start writing about it. I'll do this even before I've used the thing in question. Another writer here talks about producing versus consuming and that's the magic -- this shifts you immediately into being a producer. Most things you try and learn aren't that hard when you start actively engaging with the topic by writing about them.
2. Write test coverage. If it is a software technology then I'll start to use it by writing out the tests needed to use it. I find tests always make software technologies much more understandable because, inherently, they force you to think very atomically.
3. If I really, really want to understand something in depth then I'll create a side project about it or that requires it. Just for example I'm currently doing this as a way to force myself to build better web apps. I've chosen HotWrite and Turbo as enabling technologies and now I've got the core of a neat little app that avoids full screen redraws, uses CSS I actually understand and so on.
PS - This is the best timeline tool I've ever used. I used it to chart out my career history and it was damn useful.
https://www.preceden.com/timelines/869343-scott-johnson-care...
And don't even get me started on ranting about podcasts that don't clearly label their feed.
One of my side projects even got venture funding (and not in 2021 when things were overheated -- back in 2003).
Yes Ruby has ruined me.
I am the cofounder of Pollitify, https://www.pollitify.com/ a social network for progressive activists and the Polly software suite, a set of tools for progressive organizations.
Looking to do mutual aid in America related to food assistance / SNAP ? Sign up for a Pollitify Grant: https://www.pollitify.com/grants