I’ve often thought that the people working on herpes treatments probably don’t get the credit they deserve
Just a basic programmer living in California
I’ve often thought that the people working on herpes treatments probably don’t get the credit they deserve
Modern frameworks like Playwright do a good job of avoiding those waits. So the tests are less flaky, and are faster.
That’s a good one, and also the first thing I thought of.
There’s also a remake that’s not bad that features Hugh Laurie using his native accent.
A commit
followed by a reset
or commit --amend
later is one more step than a worktree --add
. Plus there have been lots of times when I’ve had some changes staged, and some unstaged debugging or experimental changes that I want to make sure not to commit, and thinking about how to pack all that away neatly so I could get back where I was seemed sufficiently obnoxious that I avoided doing whatever would have required a quick branch switch. Worktree would have let me pick up where I left off without having to think about it.
I’ve been using the newer commands like switch
and restore
for a while. But I learned a few things here that will indeed make my work easier.
They list the “mailing list support” feature as “WIP” so maybe the plan is to accept patches by email in the future?
Yes, this is what I think of when I think of a “dead man’s switch”. It relates to the concept of a physical device that deactivates or activates if you let go of a switch, like a light saber for example.
I think an interval of weeks would be more convenient than hours to avoid false positives. But I think Patrick Stewart’s character did daily check-ins in the movie Safe House. The dead man’s switch was actually the central plot point in that movie.
And then the replies to the reporter are also AI-generated!
I love these stories! There’s also,
And now that I’ve gone searching for these I see that they’ve all been helpfully collected on http://beza1e1.tuxen.de/lore/index.html
I think this is good advice. Don’t over-think it!