This is a very good toot thread about the concerns smashed together under “user”.
Mistakes were made in this morning's bike commuting, especially the mistake to not put on full rain gear (either at the start or at a good pause point with shelter) because it looked like only a light drizzle that I could ignore. At least I've now experienced what that's like, and everything will dry out soon enough.
(I have different clothes for the office, so at least I'm not sitting around in wet ones.)
TIL you can get black kookaburras and they are like if a wizard turned that guy from the Cure into a bird.
As always, magit for GNU Emacs is the bomb for getting me to make focused, careful commits with good commit messages. If you guessed that today's two commits were actually slammed together in the original change, you would be correct; magit's easy selective commits let me separate them out neatly.
It feels oddly good to both implement a new feature for my wiki thing (last week) and decide that it's solid enough to commit and push it to the public Github source code (now). As always, actually making the git commit pushed me to write a few more comments and so on.
To answer your unasked question: https://github.com/siebenmann/dwiki/
In a world with mutable source code and tags, people pulling things from you that you didn't intend them to is their problem; you can change your history, your tags, and your repo as you want. In a world of cached immutable modules, it is suddenly your problem. Other people have the power to easily freeze and make available your work for all time.
The Go module proxy world is making me nervous with its use of immutable, cached modules and unchangeable module checksums. The intention is good, but the real world is always more nuanced and complex than 'once someone fetches something from you it can never change and never be removed'.
(Note that I didn't say 'published'. People can fetch from you before you've officially 'published' as you consider it, or without it at all.)
That cks. Overcommitted sysadmin, photographer, bicyclist, and other multitudes. I write a lot of words for a programmer.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!