Sounds like a yes

It’s not like anyone needs to support it when I’m gone.

I have an obsidian document where I write changes I want to do in the future that I never look at; does that count?

That’s the neat part, I don’t.

It can, if it’s passed through to tools without the llm meddling, but the problem is that there is typically a tool for arbitrary shell commands, and unless there’s a mechanism to dry run these, there’s no way to handle it reliably.

And yet here you are

I bet you’re fun at parties

Eaux in French is pronounced like o

So foo -> feauxeaux

I have a project with a bunch of compose files that define the services I self host. I “deploy” the project by sshing into my server and doing “git pull” which means I’m often making changes that don’t get tested before committing to source control. As a result I have long chains of commits like:

• refactor the sproingy widget
• refactor the sproingy widget v2
• refactor the sproingy widget working
• maybe the sproingy widget works this time?
• ok finally found the issue with refactor sproingy widget
• fix formatting of sproingy widget

And now I’m wondering if I’ve been an llm this whole time

I need programming courses for swimmers

I set up split dns using a phone earlier this year, and it’s been fantastic

All future versions of Python should just append digits of pi; semantic versioning be damned

It’s the main reason I use findroid

Now do Linux

Humans were still very much the weak link here. The tools to do this even mildly securely are available, well documented, and honestly, cheap af

For that matter, August has to use a blank in the first position as well

Febrauary?

That doesn’t give me a memorable mnemonic though.

tar -eXtract Ze Vucking File

It doesn’t seem very useful