Also the happy path for my save state is just flick away from the given labeled shell/emacs in tmux. Some things need a note jotted down but then I have failed

Also the happy path for my save state is just flick away from the given labeled shell/emacs in tmux. Some things need a note jotted down but then I have failed to do something earlier. Sometimes he thing to save state is just put in a syntax error where I am working; that way I can afford to forgot the task altogether. All these pending tasks bear only a light resemblance to the project tracking entities. For that project stuff, I mostly fight to reserve bandwidth among the team to work on long term projects that are experimental (and so not always plannable in advance In detail) but with a highly desirable end state. Like now I am working to make good terraform modules that make the common use cases of change to be simpler and more concise than without the modules. We find a good use case, do a module, iterate a few times based on how it works out, then find a other use case. I refuse to “write stories” for the future tasks in this extremely valuable work because it’s a back and forth between solution space and actual work for actual customers. I don’t need giant modules that are as complex as the raw terraform, I need to solve specific problems in the specific business.