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 o

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 :)