Comment by mschaef
1 day ago
After trying text files and other apps, I wrote my own about ten years ago and have been using it ever since. ( https://famplan.io - I'm starting to turn it into something other people might use.)
I tend to agree with the idea that simpler is better, but a single text file wasn't quite enough. I like being able to see my lists on multiple devices, I tend to like to have multiple lists for different purposes, and it's also very useful to have shared lists for coordinating with my family and others.
The experience of using this has taught me a few things about how to use these lists effectively:
1. Using a list is like writing a journal - you need to be intentional about explicitly working to make it part of your routine. (Part of this is committing to record tasks that need to be done and then committing in some explicit way to actually doing those things.)
2. It needs to be fast, it needs to be easy, and it needs to be present. Anything else gets in the way of point 1.
3. It's important to track when you need/want to do, but lists of things to do can be overwhelming. (It's useful to have at least a few ways to ignore items when you can't or don't want to deal with them. I handle this by having multiple lists, and also having a snooze feature to ignore items for a while.)
4. You need to have a way to handle items or tasks that go on for a while. (You need to make a call, but have to leave a message, and are waiting for a callback... etc. These are places where you need to take action to push something along, but the action doesn't result in a complete task, so you need to revisit it later.)
This is going to sound odd coming from someone who wrote a tool for the purpose, but the key here is really to pick a system (any system) and then actually use it. Spend too much time developing the system, then all you've done is give yourself something else to do.
I tried '4famplan4' as my password just to try it, and it said password insufficiently complex so I backed out. :(
Thanks for trying. (It expects mixed-case, which I need to actually say in the messaging.)
The codebase started out as something I used entirely myself, so the aspects of the workflow that relate to new user onboarding (most important for actually getting customers) are the ones that are the weakest. So this part of the codebase is where I'm working now to clean it up and it's probably also the most rough.
Why does it require mixed-case? It's for TODOs, not healthcare. If I want to use my insecure password to try out your service, please let me! It took extra code here for you to try to be secure, when it's now generally known that password requirements are security theatre at best and anti-security at worst.
2 replies →