@JohnHMcWhorter@lexiconvalley Really surprised at this idea that hares is some kind of academic term. As a Brit the word feels very normal. I live in Gothenburg, Sweden where there are a Lot of hares anywhere there’s green space - they feel like a quite different beast: instantly recognisable and distinct.
@bonsaistudio@nvictorme@housecor I feel like people are somehow scared of the concept of rebasing, maybe because it's an unfamiliar word, maybe because it's not something they're initially exposed to.
Which is a shame, because to me it feels conceptually MUCH simpler than a merge.
@TkDodo@housecor To be clear I'm not trying to say "this is the only way to do it and all other ways are plain wrong", more like "I tangibly experience the value of doing it this way, on a pretty regular basis" and that's why I think yes, it is worth it.
@TkDodo@housecor iii. I completely disagree that the record of the mistake is useful: in my experience leaving it unsquashed more often leads to the reader _repeating_ the mistake, because we're usually finding commits via blaming lines, not reading the history sequentially.
@TkDodo@housecor i. For me it renders the commit messages kind of useless, since they're misleading: the message for 1 says it's the change x, but actually change x is the combination of 1, part of 2 and 3. It's work for a future reader to reassemble that context.
@TkDodo@housecor I think we're talking about two different things: I'm definitely not a fan of squashing *features* down to a single commit. I'm talking about when the commit history looks like:
1. change to x
2. case missed in x, plus a change to y
3. fix typo in x
None of these are meaningful
@TkDodo@housecor For me commit messages can be incredibly useful documentation of why code is the way it is, and squashing commits into meaningful changes is necessary to make that happen.
When a change is split over multiple commits, we’re asking the future reader to do work to understand it.
@avdi Do you have an opinion on The Prime Directive of Retrospectives? https://t.co/f3DXVrMZbS
It feels like it calls for "assume positive intent" in a specific bounded context, trying to avoid the opposite (assigning blame, which usually doesn't end well).
Finally removed Octopress dependencies from my Jekyll blog (Octopress has been unmaintained for many years now) and wrote some thoughts about the arc and vision of that project: https://t.co/R768hO9bNX
Still not getting used to hearing the @_bikeshed podcast talking about I gem I'm a maintainer on (Pundit). I mean I didn't develop any of the features they're complimenting, but still.
@dxw https://t.co/MI1MGO2o8k seems to sensibly show the site description instead. Also nice to see that the ?author=1 query still refers to almighty zule
In need of expert WP advice, I turn to my old accomplices at @dxw: a site for the nonprofit dance association I’m part of https://t.co/KRluLmDVW3, shows the main site author in the share block when shared to discord, instead of the site description. Discord is calling ?author=1 ?