hallettj

It looks like there is a playlist here: https://youtube.com/playlist?list=PL-cwa6ZvflaDvviwm8JqO6hZ9W-fhG48c&si=SLCAv2EqJ_jRC9fj

Probably not very similar, but Git Butler is very interesting. It adds its own layer of management so that you can have multiple branches “applied” to your working tree simultaneously. It’s helpful when you have multiple changes that should go into different branches, and some that shouldn’t be committed - it has a system of lanes that help keep track of all that. Or you can test how changes from two branches interact.

Last time I used it, maybe 6 months ago, it was rough around the edges so I didn’t stick with it. But they’ve done lots of work since then so I’m thinking of giving it another go. It is (last I checked) an all-in tool. When you’re using Butler on a project you probably won’t be able to use other git tools.

I think it depends. Lua is great for scripting - like when X happens do Y. I agree that makes sense for a case like Home Assistant. Sometimes you really want the result to be a data structure, not an interactive program, in which case I think more sophisticated configuration (as opposed to scripting) languages might be better.

Yes, there’s a good example. Ansible would make more sense if its configuration language was Nix…

Oh, thanks for calling that out. I think I may have mixed up some of the frustrations I experienced at an old job.

I agree - YAML is not suitable for complex cases that people use it in, like Terraform and Home Assistant. My pet peeve is a YAML config in a situation that really calls for more abstraction, like functions and variables. I’d like to see more use of the class of configuration languages that support that stuff, like Dhall, Cue, and Nickel.

There is another gotcha which is that YAML has more room for ambiguity than, say, JSON. YAML has a lot of ways to say true and false, and it’s implicit quoting is a bit complex. So some values that you expect to be strings might be interpreted as something els.

I use metric temperature when I talk to my kids. Now they give me a hard time when I give them a Fahrenheit value! Keeps me honest I guess. I’ve also got my oldest using a 24 hour clock.

Stardate, 2024-08-30T06:34:17.993Z

Zed invented tree-sitter which is a great feature. But since tree-sitter is open source it’s also available in neovim and helix.

That’s a different form

I think this is good advice. Don’t over-think it!

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?

Until I read the caption I thought I was looking at giant fingers grabbing the dwarf to stick him in the computer slot

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,

• radioactive cows
• the high-tide bug
• OpenOffice does not print on Tuesdays

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