Unintentional perfection

We were following¹ a luxury car down the road this afternoon and it kept suddenly slowing to a crawl for no apparent reason before resuming normal driving for a few blissful minutes. My spouse wondered aloud if the issue came with driving an "XFinity"?

It's just as well she was driving because I couldn't control my laughter for minutes afterward. That outfit of jokers provides what I have to laugh to call our internet "service" and it behaves just like that car.

She swears it wasn't premeditated, but it was beautiful.

---

¹ At a respectful distance. This didn't seem to be some kind of "crazy Ivan" stunt.

A Modest Proposal

I believe proper consideration should be given to the benefits of creating an affirmative defense to charges of assault and battery in the case that the assaultee¹ is a telemarketer.

Now, I'm aware that some people will maintain that only the most hard-up and vulnerable of people will actually take some jobs which is a valuable point. Perhaps the defense could be limited to people of authority in such anti-social enterprises. Say, starting with shift-managers and working up from there certainly to include the technologists who support and enable the whole industry.

---

¹ Note: not "victim", they are very much at fault in the whole interaction.

Now what?

Challenge of the day:

Search the web for a git workflow that is suitable for cases where you need to take a sub-module through a non-trivial evolution (that is something you'll be working on for a while, making multiple commits on and want to share with your colleagues as you go).

Go ahead. I'll wait. Probably for quite a long time.

You see, the web is teaming with tutorials and workflow articles on submodules, but they rarely get farther than setting up a repository and/or checking one out. At that point the article is already too long for a blog post: you readers are bored and have deleted the browser tab displaying your hard-won expertise.

I thinking of trying something like

1. Create a pair of custom branches with the same name in the parent and child repositories.
2. In the parent, edit .gitmodules to point at the branch im the child.
3. In the child do the first step of your evolution.
4. Push both and inform your colleagues
5. Continue working in the child; push and inform your colleagues when appropriate.
6. Once your colleagues have approved the work, merge your branch in the child to whatever the main development branch is.
7. Edit .gitmodules in the parent to point to the merged code.
8. Push both and inform your colleagues.

Idle curiosity

What was the ratio of torches to pitchforks when the mob came to make Linus pay for git submodule?