I like that. It seems the internet with theoretically good answers for things that can be difficult to find. Blog format is much easier to skim that SO, and as long as the post titles are valid and meaningful, it’s a quick check for usefulness before reading.

I was just thinking the other day how nice it would be to port pamac into some more prod-oriented environments.

Looking through the docs, it appears to tick most of the boxes I’d want, will have to play with it in the coming days.

Have an upcoming project that will actually require some consistency and documentation, this might be useful.

I don’t mind building when necessary, but doing so is not calculated to communicate well with future me, so it’s not ideal.

Betteridge’s Law of Headlines - I find it has near universal applicability.

If their comfort level is limited due to lack of experience, I tend to sandbox them somehow and then walk them through a couple examples of “danger” vs “ok, this definitely won’t be irreversibel if it’s wrong, but I think it will do what I want.”

A couple of my go tos are the obvious rm -rf / vs ./ and a sed with and without -i on some random text file.

That naturally segues to “here’s the man page, here’s how to use it and search it.”

That tends to give them some confidence that they won’t accidentally cause real damage, and make it seem like they aren’t just typing arcane magic spells, but actually understanding how to responsibly put the pieces together.

I’m not sure I agree - your definition would almost certainly include the kernel, office suites, and a host of other things.