Apparently, this is a dogfood burger. No idea why that exists, but I’ll take it, because I’m definitely dogfooding.
I’m building a build system. And I’ve got three previous/ongoing projects where I’m directly integrating it.
And yeah, I’ve noticed that I’m kind of jumping between features, always just building them as far as I need them.
And in particular, I’m not really planning ahead. For exanple, I noticed after the fact that I could easily pull out a whole feature into a separate library, and that would already be useful on its own.
But on the plus side, it’s much easier to figure out actual requirements this way.
I usually keep todo-lists, where I’ve kind of noted down the next few steps for each feature. And well, those then usually also contain infos for the step I’m currently working on or for previously completed steps.
I rarely actually stick to my planned next steps, but it does help when switching between contexts, if that’s why you’re asking.
Apparently, this is a dogfood burger. No idea why that exists, but I’ll take it, because I’m definitely dogfooding.
I’m building a build system. And I’ve got three previous/ongoing projects where I’m directly integrating it.
And yeah, I’ve noticed that I’m kind of jumping between features, always just building them as far as I need them.
And in particular, I’m not really planning ahead. For exanple, I noticed after the fact that I could easily pull out a whole feature into a separate library, and that would already be useful on its own.
But on the plus side, it’s much easier to figure out actual requirements this way.
Do you keep a regular log of the work that you do? Beyond the commit messages I mean.
I usually keep todo-lists, where I’ve kind of noted down the next few steps for each feature. And well, those then usually also contain infos for the step I’m currently working on or for previously completed steps.
I rarely actually stick to my planned next steps, but it does help when switching between contexts, if that’s why you’re asking.