It reads a bit like my current position after two decades of on-and-off-GTD and ~three years of PARA: the project/area/resource distinction is practical, but not earth-shattering.
But what‘s really working is GTD, which the article doesn‘t call out, but implicitly lumps together with PARA: actionable next tasks and collecting everything in some kind of inbox.
I haven‘t found much use for PARA itself in my personal life, but for organizing my work OneDrive it shines.
For organization, I found that Johnny Decimal is my perfect sweet spot.
Seconded on GTD, or at least a version of it. I suck at consulting an app about what I could be doing in a given context. I’ve mostly discarded that, other than things like shopping lists and 1:1 meetings. But the idea of capturing every action I need to take, then routinely putting those in home/work/self/etc. buckets was life changing. I’m a devotee to that habit.
Have you seen my recent ‘task and project management’ course? I’m really happy with how the task part worked out, and feedback has been universally positive.
The project side has work to do. I think I’ve solved the problem and will be updating the course in the next month.
Seek is annoying, because it throws up some kind of „please don‘t disturb nature“ dialog box every time you start it to take a photo. I hve seen that warning hundreds of times, why can‘t i disable it after a few confirmations?
I‘ve moved to the main iNaturalist app, and it does everything Seek does, but better and it’s generally also faster.
Your wife’s Python version is quite impressive. It wouldn’t have occurred to me to do the simple thing and just do some string-replacement targeted at a narrow use-case instead of using a complicated templating engine.
> just do some string-replacement targeted at a narrow use-case instead of using a complicated templating engine.
A neat little in-between "string replacements" and "flown blown templating" is doing something like what hiccup introduced, basically using built-in data structures as the template. Hiccup looks something like this:
(h/html [:span {:class "foo"} "bar"])
And you get both the power of templates, something easier than "templating engine" and with the extra benefit of being able to use your normal programming language functions to build the "templates".
I also implemented something similar myself (called niccup) that also does the whole "data to html" shebang but with Nix and only built-in Nix types. So for my own website/blog, I basically do things like this:
Back when I used it the mobile app on iOS was broken, but they fixed it real quick. That was encouraging.
Other than that, I mostly stopped using it because it forces you to regularly rotate all certificates, and for my personal purposes it was too much of a hassle.
I still like the project a lot and wish it would be more prominent. Nowadays everyone immediately seems to recommend Tailscale.
But what‘s really working is GTD, which the article doesn‘t call out, but implicitly lumps together with PARA: actionable next tasks and collecting everything in some kind of inbox.
I haven‘t found much use for PARA itself in my personal life, but for organizing my work OneDrive it shines.
reply