3 ms·

Great concept. Tempting, but the digital version I set up saves a bit of drudgework with the pen and could be a little more private. [0] I like the bullet sign

by luxpir 10y ago

Great concept. Tempting, but the digital version I set up saves a bit of drudgework with the pen and could be a little more private. [0] I like the bullet signifiers. I split events and tasks into calendar and todo list, but the bullets could work in a long, timestamped single file. Perhaps using # to comment out lines that are complete. Might make more sense than the archiving I do by moving to the bottom of the todo list. Actually, my calendar events comment out the done lines, so perhaps the todo really should too. Anyway, good share. [0] https://github.com/luxpir/plaintext-productivity https://github.com/luxpir/plaintext-productivity

jiiam 10y ago
Nice, but IMO it falls, as the Bullet Journal, into the category of beauty over result. I just think that simpler, less structured systems provide comparable results in terms of getting things done, while wasting less effort on the nonessential aspect of system. As for alternatives, my favourite is t (http://stevelosh.com/projects/t/ http://stevelosh.com/projects/t/). Truth be told, it may be way too simple. But yet again, complexity needs to be justified. As a side note, remember that you can do for organizing tasks an argument similar to xkcd's on automation: https://xkcd.com/1205/ https://xkcd.com/1205/ https://xkcd.com/1319/ https://xkcd.com/1319/
- luxpir 10y ago
  Suspect we're singing from same hymn sheet. Not sure if you read the linked blog post but the idea was to cut complexity and to push back against the creation of endless to-dos into a pit of unending pain. A no-cruft list, with some kanban features, but zero-code was the plan. t is not more simple than a plain text file. It invariably contains hundreds of lines of code and encourages you to throw tasks into an invisible task-pit. So yeah, I think it's a case of whatever works for the individual, but pruning and preening an organisational system, constant reviewing and decision-making about the list itself; that's not what I had in mind. Cheers for looking :)
kzisme 10y ago
For others - https://lukespear.co.uk/plaintext-productivity https://lukespear.co.uk/plaintext-productivity Blog post linked to the repo

by luxpir 10y ago

jiiam 10y ago

Nice, but IMO it falls, as the Bullet Journal, into the category of beauty over result. I just think that simpler, less structured systems provide comparable results in terms of getting things done, while wasting less effort on the nonessential aspect of system. As for alternatives, my favourite is t (http://stevelosh.com/projects/t/ http://stevelosh.com/projects/t/). Truth be told, it may be way too simple. But yet again, complexity needs to be justified. As a side note, remember that you can do for organizing tasks an argument similar to xkcd's on automation: https://xkcd.com/1205/ https://xkcd.com/1205/ https://xkcd.com/1319/ https://xkcd.com/1319/

luxpir 10y ago
Suspect we're singing from same hymn sheet. Not sure if you read the linked blog post but the idea was to cut complexity and to push back against the creation of endless to-dos into a pit of unending pain. A no-cruft list, with some kanban features, but zero-code was the plan. t is not more simple than a plain text file. It invariably contains hundreds of lines of code and encourages you to throw tasks into an invisible task-pit. So yeah, I think it's a case of whatever works for the individual, but pruning and preening an organisational system, constant reviewing and decision-making about the list itself; that's not what I had in mind. Cheers for looking :)

kzisme 10y ago

For others - https://lukespear.co.uk/plaintext-productivity https://lukespear.co.uk/plaintext-productivity Blog post linked to the repo