Ansible playbook is perfect for this. All your configuration is repeatable, whether on a running system or a new one. Plus you can start with a completely fresh newest version image and apply from there, instead of starting from a soon-to-be outdated custom image.

Postgres handles NoSQL better than many dedicated NoSQL database management systems. I kept telling another team to at least evaluate it for that purpose - but they knew better and now they are stuck with managing the MongoDB stack because they are the only ones that use it. Postgres is able to do everything they use out of the box. It just doesn’t sound as fancy and hip.

Also, Kanban was invented in the 40s as a process for automotive production lines. That’s why it aligns so well with maintenance and operations projects in IT. It’s ridiculous how more and more people claim it comes from software development and would not fit hardware projects, when that’s the core use case of the methodology.

When I installed Kinoite to start using Linux as my primary daily driver, the first thing I did was setting up Ansible, creating a new playbook and all Linux configurations I made from that point on, are only ever done through that playbook, which is backed up in my Forgejo instance. One command and everything is being set up exactly the way I want. It feels extremely liberating.

To me it feels like it doesn’t do much better than the Google keyboard. But it does follow my custom dictionary while swiping, which Google never did. After all these years it still suggested a word I never use instead of a name I type often. Heliboard just casualty does the correct thing after adding the name to the dictionary. That plus showing the detected word directly above the finger so I can keep my eyes on one spot instead of constantly checking the text for bullshit words are killer features to me.

It depends. Some hardware degrades gracefully while my current desktop system won’t even boot and throws error codes on an empty battery. It took me hours to figure out what was wrong the first time it happened.

Coffee seems to be a self enforcing meme at this point. It’s not unhealthy enough to have suffered the same fate as cigarettes. Which had pretty much the same jokes not too long ago.

It turns out there’s still plenty I don’t know, and I spend much more of my time confused and frustrated than I did before. The cool part is that I’m now confused and frustrated by really interesting problems.

This is spot on. Your whole response ist just a trove of insight, I wouldn’t have been able to articulate so eloquently.

Paperless -> Paperless-ng -> Paperless-ngx

Yeah, it’s the same for me. The content is awesome but requires a lot of concentration.

As you mentioned, with Fedora the best alternatives are immutable spins. Updating means downloading a new base image, applying overlays and additional installations to it and on the next reboot you start from that image. You can configure it to keep as many previous versions as you need and boot into those directly on startup. Since you never change your current image once it’s built, you can’t break a known good system. You can only ever break your next version and in that case, just boot the previous.

I’ve created an Ansible playbook that configures a vanilla Kinoite the way I want it. No need to back up the system if I can recreate it with less than a megabyte of text files. Secrets are in my password vault, personal files are in my personal cloud and get synced to and from the laptop continuously. I would never go back to backing up system files as opposed to recreating it with a playbook. That seems so wasteful in hindsight.

Flatpak with Fedora 39 must have come a long way. Almost every tutorial with workarounds or discussion of broken features you can find online is now obsolete. It just works out of the box, especially under KDE. Mostly. That makes searching for actual issues extremely hard because I find myself chasing down paths of issues that have long been resolved.

Yeah, I removed Firefox from the layers as well and use it via flatpak. Somehow that felt appropriate from a security perspective, to have it sandboxed.

The Lenovo business models (ThinkPad series) are amazing value. My 11 year old laptop is still going strong.

Just stay far away from any Lenovo non-business models.

Exactly this. This procedure is so common that you need to take care in situations where you don’t want the headers, as some tools set them per default.

[…] and velocity is often used to compare developers against each other.

Wow, that’s messed up. Luckily I’ve never had such a team/such leadership.

It’s not flawed. Nobody should get rewarded or encouraged by story points. It’s solely a planning metric and not a metric of productivity.

Everyone keeps saying that but I just can’t see it. The only time my mails were rejected was because I didn’t know what I was doing at the beginning of my journey. Now, whenever I changed my stack or did some major updates the past 20 years or so, I just go to 2-3 sites that analyze my mail server from the outside and tell me if there is anything wrong. The free tier is always more than enough. Just make sure there is at least one service in the list where you send an email to a generated mailbox and have it analyzed. Just looking at the mail server is not enough to find all potential configuration issues.

I aim at a100% score. It’s time consuming the first time around but later it’s just a breeze.

Who asked about Threema?

The comment above me started that topic. The one I responded to and you seemingly haven’t read.

Threema is very security focused at the expense of user experience. You lost your private key? Tough luck, here’s a new account and everyone will have to verify your new account again. I have had conversations with friends over five or six of their accounts because they use threema just like WhatsApp. I stopped recommending threema to folks without a basic technical understanding. Signal is more than good enough for their needs.