3 ms·

I use github projects with a Research/Maybe, Todo, In Progress, Testing, and Done columns. Each item has a checklist of steps needed to complete the item. For e

I use github projects with a Research/Maybe, Todo, In Progress, Testing, and Done columns. Each item has a checklist of steps needed to complete the item. For example, I might have an item that is "Workers have an inventory" and a bunch of steps to do that "Add an inventory component, add a take item event, etc." that are markdown checkboxes. This lets me do some 'design' via listing out all the classes/touchpoints, while still giving me the flexibility to tear stuff up, shuffle it around, and not lose state. I'll also often keep one text file with very tactical todos, stuff I was in the middle of typing out when interrupted, so I can quickly get back into flow state.

K0SM0S 7y ago
I do pretty much the same manually with Kanbanflow (columns represent days, leftmost is "now/current", rightmost is whatever's pushed later to my next sprint). I combine this with a pomodoro color-code for "short/easy" (1 pomo), "medium" (2-3 pomo), "long/hard" (4+) and plan my day. I took this from uncle Bob, you just give things a rating (unitless). "Oh, that's a 6, no less!", "oh that's a 2 at most". It's enough for development (I find it's only management that wants more 'reporting' and 'estimates', being solo I do that in medias res, i.e. on the spot). However you got me curious with github projects. It seems it would integrate better for programming / design. I definitely have to experiment! Any tips to boot?