Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Thanks! Most of the "how" is shared in another reply. Really it's just an array of strings that keeps a cursor (and technically a stack for interruptions that pop off before returning to the cursor in the list). So posting a fresh list to the service that runs it is a common use case. Loading saved lists, routines, some things have state machines that inform task creation but that complexity I wax and wane finding all that useful.

The book "the checklist manifesto" informed some of this philosophy behind the tool(s). To learn new things specifically is spaced repetition and keeping a backlog of things to dig into. One practice that has stuck is a list of reminders / active ongoing things that I burn through when making a hotlist. If I'm good I'll actually do what I load, if I'm not I'll load it with good intentions and skip things or take it out as the day gets hectic. Nothing really more than you'd do without the one item at a time system.

It's all a work in progress and malleable since it's exclusively mine. If I come up with a better way then maybe that's what it will morph into.



Actually, there's the other aspect of "learning things" which is if I want software to do something I just build it and usually I've never done it before. The elisp emacs functions, the Android launcher, the swift taskbar menu thing, global hotkeys on windows in c++, data only push notifications, background services on all the things. Just a good excuse to roll up my sleeves and get some code written for something I otherwise have no business digging into. It's fun and keeps me well rounded.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: