43 lines
2.3 KiB
Plaintext
43 lines
2.3 KiB
Plaintext
= poms =
|
|
|
|
A very opinionated companion for taskwarrior, with notes and the pomodoro technique.
|
|
Designed to help you overcome being overwhelmed
|
|
|
|
= workflow =
|
|
|
|
- You pick a list of tasks you think you can achieve in the time you have alotted.
|
|
- A good reference for this is [cblgh's 12pom days](https://cblgh.org/12%20pomodoro%20workday/)
|
|
- Each of the tasks you list get placed into a text file.
|
|
- This textfile is free to use as you see fit.
|
|
- I make plan textfiles, and I generally link my task-note into that, and write about the specific task in there.
|
|
- Once you feel like you've got an adequate plan for each of your tasks, you can exit your editor.
|
|
- You'll get to choose which task to work on next
|
|
- Now you're in Pomodoro mode. Do the task! Take more notes with a shortcut.
|
|
- Now it's break time!
|
|
- Rinse, repeat until you're done!
|
|
|
|
= Roadmap / Issues =
|
|
|
|
- Implement state machine to manage state (See design docs)
|
|
- Timer spinner
|
|
- Timer counts down
|
|
- Task marked as `start`ed once timer begins
|
|
- Ask if task completed on end of timer
|
|
- Set break timer
|
|
- Loop continues once break is completed
|
|
- TaskList Active tasks should _always_ display, and then let the cursor indexing kick in
|
|
- Full screen application
|
|
- Dynamic column spacing based on WindowResizeMsg
|
|
- When going from TaskList to nvim, don't overwrite! Ask!
|
|
- Show hints about actions / shortcuts on screen (help information)
|
|
- Refactor extra functions out of `main.go` and into `task.go`
|
|
- Make sure task loading happens through `tea.Cmd`
|
|
- Set up debugging environment?
|
|
|
|
= Associated Tooling =
|
|
When developing this I also realized I need associated tooling to help manage my backlog more generally.
|
|
Similar to how I have a task selection section here, for which tasks will be active, I think I also want a backlogger and de-backlogger, for putting things into and out of my backlog easily. I was thinking that things that get backlogged in this way should also get a `recently backlogged` tag or something so that I can sort them easily, but then I thought there should also be a script which removes the recently tag after some time, and then I wondered if I'm just over engineering this for no fucking reason, I don't need cascading backlogs???
|
|
|
|
= Design Docs =
|
|
- [Excalidraw drawings](https://excalidraw.com/#json=Tucrdp__TOwmtOEvNnbVv,ep_J-9-vB3BRVjnd0Y2H0w)
|