233
My latest personal project would look like this:
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Aug 2024
233 points (94.6% liked)
Programmer Humor
19854 readers
1782 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
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.