Return to Answer

TBH a lot of my commits which follow that "Working on [...]" log pattern are not modeling coherent units of change (why I often cannot come up with a message better than "Working on [...]") but just the result of me taking a breather, like making myself a cup of coffee. The "Completed [...]" message indicates the end of that unit of work, and there I often write a much more detailed message along with the first "Started working on [...]" type messages when I just start working on something.

TBH a lot of my commits which follow that "Working on [...]" log pattern are not modeling coherent units of change (why I often cannot come up with a message better than "Working on [...]") but just the result of me taking a breather, like making myself a cup of coffee. The "Completed [...]" message indicates the end of that unit of work, and there I often write a much more detailed message along with the first "Started working on [...]" type messages when I just start working on something. If you average commits like once every 15 mins, then those "Working on [...]" messages are more like in-betweeners for what someone might commit in one bulkier commit with a more detailed message.

I just go ahead and commit it before even running tests sometimes (again if I had an unexpected event). Also even though I'm solo, I do push to a server (just one running here at home on a LAN) that does CI. That might seem like overkill but dunno, I got so used to leaning on that in my former workplaces. Plus I don't wanna be bothered having to run all my unit and integration tests by hand each time. I like having that all tied to just pushing. If a test fails it's easy enough to work in a forward-moving fashion where I do the regression, correct the mistake in the latest rev, and keep going.

I just go ahead and commit it before even running tests sometimes (again if I had an unexpected event). Also even though I'm solo, I do push to a server (just one running here at home on a LAN) that does CI. That might seem like overkill but dunno, I got so used to leaning on that in my former workplaces. Plus I don't wanna be bothered having to run all my unit and integration tests by hand each time. I like having that all tied to just pushing. If a test fails it's easy enough to work in a forward-moving fashion where I do the regression, correct the mistake in the latest rev, and keep going. That said, I do at least build the code against a debug build before I commit.

Oh and sometimes I get a bit drunk after I leave and it's usually a bad idea to try to write complex code while drunk. If I attempt to do that, at least I committed the soberly-written code before I left to revert back towards instead of mixing the drunk code with the sober code, at which point my commit log might read like, "Reverting back to code written before Jagermeister shots."

Oh and sometimes I get a bit drunk after I leave and it's usually a bad idea to try to write complex code while drunk (though not always; one time I came up with a really nice context menu system after having an eureka moment while drunk, but I only had like 6 beers and it wasn't that complex to code). If I attempt to do that, at least I committed the soberly-written code before I left to revert back towards instead of mixing the drunk code with the sober code, at which point my commit log might read like, "Reverting back to code written before Jagermeister shots." I don't do this very frequently unless I got a drunken code inspiration, but in those rare cases, it really did help that I committed something before I went out and got drunk.