6 ms·
I'm insane, so I just create a parent task in taskwarrior: "build real estate app for client x" Then anything that falls directly under that is a blocking task
by darau1 7y ago
I'm insane, so I just create a parent task in taskwarrior: "build real estate app for client x"
Then anything that falls directly under that is a blocking task:
- "build backend to serve api"
- "build frontend" (this might be blocked by the one above, or not, depending on what it really does)
- repeat ad naueseum until those big tasks are broken down enough for me to visualize
Using a project might be nice to get a progress bar, but sometimes something I need to do doesn't fall exactly under this project, or might affect existing projects:
- increase block storage for shared server
So I just use a single, parent task, and have child tasks that block it. That way I always know what to do next, and I keep going until it's all done.
- jordwest 7y agoThis is the same process I use on a whiteboard to plan out complex projects at work with my team. It's a nice way to see what tasks can be worked on simultaneously in non-solo work too. As a side project I'm currently working on a tool to do this planning visually.
- darau1 7y agoMy sole gripe with TW is the lack of a pretty GUI and a power mobile app. Both problems I can solve on my own, mind you, but still... Plus I know it'll be a huge problem if I ever have to work with anyone else.