|
|
|
|
|
|
by vi1rus
2764 days ago
|
|
|
How do you keep track of your queue? Also is it FIFO, LIFO or a priority model? My queue seems to bloat, then I tried to mitigated that by telling myself if something is in the queue for X amount of time remove it. Nowadays that removal just becomes a JIRA story but it's rather inefficient for me. |
|
|
That usually means I end up sort of ping-ponging between feature development and refactoring/tech debt. I develop features until I feel like structural issues are annoying/slowing me down, and then I focus on code quality until I can move fast again.
But honestly it's a very loose system and it's fairly sensitive to what I am most driven to work on in a particular time period. But I'm not really trying to micro-optimize the project, my main goal is to have a system which lets me be consistently productive. That means it's loose enough to not get in my way when I'm in flow-state, and it's organized enough that I can have a list of achievable goals to work through when I'm lacking in intrinsic motivation.
I also don't mind having a pretty huge back-log. When I'm totally uninspired it's nice to be able to pick up on ideas I haven't thought about in weeks and play around with them with fresh eyes.
edit:
> It's a pretty loose priority system, with the basic heuristic being that I try to choose the task that brings the most value to the project at the given moment.
I built my own very simple tool for that. It's a bit redundant since there's a lot of great tools out there, but it does everything I want and nothing I don't, and it's very low friction/distraction free.