I struggled to attract competent Rust engineers, the company wasn't flashy enough, I suppose. Therefore, I had to step in to prevent the entire migration of our infrastructure to fail.

Migration went smooth. We had 2 hours of downtime to move terabytes of data and millions of users.

Go was carefully chosen so that it could be maintained by the devops folks. I don't like go, not even the slightest but it was a sensible choice. He didn't like it and went entirely rogue and rewrote the tool in Rust behind my back. This, and a few other things, made me let him go after this.

For example, user creation. I can invoke `useradd` but it's not idempotent, and to make it so, I would have to figure out how to query it before executing it. With Ansible, it's just `ansible.builtin.user`.

Less on Ansible Galaxy, I only have two or three roles that I use. I believe Ansible is really valuable because it integrates so many standard workflows directly, which are idempotent by default (i.e everything in ansible.builtin.*).

PyInfra, for example, is a glorified SSH abstraction.

I'm interested in what you come up with. I looked into PyInfra, but went back to Ansible because the ecosystem was so worth it.

That's how everyone has started. You'll do fine.

I don't know why, but I know it's not an account or history. This is by design. And it extends to other libc's as well (musl, for example, does not offer dlopen when statically linked).

Wanted to ping Rich Felker, but he seems to have vanished from Bsky.

I'm curious, what do you regularly use a linked list for?

Sorry to hear that. It's true, unfortunately. Seen similar things too often.

Especially with today's hardware, it is not necessary to update hardware every two years (or less). I'm still mad at Microsoft for rendering my perfectly fine gaming PC useless with lack of Windows 11 support.

I haven't had to use a linked list in the first place too often. Only one a handful of embedded projects.

What the fuck @mozilla.org ? You were the chosen one to not do this bullshit.

It does make sense. It's challenging to work in isolation. I've been there, and I've managed folks 9 hours behind me. Made collaboration really difficult.

Ahh! Yes, that's what I remembered. I must've missed that. Thank you!

Sounds intriguing. Do you still require folks to be available at US hours? (Used to be part of the descriptions, seems to be missing here)