61–70 of 72 posts
I read, I play, and then I write an interactive page about the thing. E. g. https://wordsandbuttons.online/complex_numbers_and_conformal...
A shortcut that I use for learning new technologies is to learn their pitfalls and tips. For example: I want to learn the PostGIS PostgreSQL extension. I install the extension and make a sample database with PostGIS datatypes. Then I will make a bunch of the following searches: "postgis gotchas", "postgis tips and tricks", "postgis common mistakes", etc. Open everything you find in a new tab. Then I will edit the sam…
He doesn’t deliberately teach you incorrectly but he’ll set up the project in such a way that when he asks you to add X he expects the vast majority will think “oh I just do this” which doesn’t work because the real answer is a bit more involved. Bonus: when you start spotting the pitfalls ahead of time it’s super motivating!
1. Find a new note-taking app 2. Spend a couple hours configuring it 3. Install a bunch of extensions 4. Run into some obscure bug, spend a couple hours debugging it 5. Report the issue 6. Go to bed, satisfied with how productive I've been
People who use second-brain knowledge systems spend more time writing about, than actually using them — so 7) would be blogging about it.
The most important thing for me to really cement something is producing (vs consuming). Reading docs, watching videos... those are consuming. Of course you do have to do these things to get started. When most hackers thing of producing they probably think of building something - meaning coding a small project - but for me, to really really learn something, absolutely nothing comes close to teaching it to someone else…
I may steal this method.
Earlier quoted context omitted.
People who use second-brain knowledge systems spend more time writing about, than actually using them — so 7) would be blogging about it.
Killer apps are hard to find. I recently thought to myself “I have notes scattered across five different services, I should consolidate them” - so I dove into Obsidian, got it all set up to cloud sync, transcribed some of my existing notes, categorized them, aaaaaaand… a year later, I now have notes scattered across six different services.
This is why I learned to just accept imperfect systems.
Perfect systems just don’t exist.
For the time being I’ve settled on mediawiki per notes and digital garden.
Ymmv.
A shortcut that I use for learning new technologies is to learn their pitfalls and tips. For example: I want to learn the PostGIS PostgreSQL extension. I install the extension and make a sample database with PostGIS datatypes. Then I will make a bunch of the following searches: "postgis gotchas", "postgis tips and tricks", "postgis common mistakes", etc. Open everything you find in a new tab. Then I will edit the sam…
1. Find a new note-taking app 2. Spend a couple hours configuring it 3. Install a bunch of extensions 4. Run into some obscure bug, spend a couple hours debugging it 5. Report the issue 6. Go to bed, satisfied with how productive I've been
My notion configuration is so complex now, api posts, conditional formatting and quirky ui features...but I'm still a human blob.