Feuerfest

For an upcoming blog article I wanted to include a link to a blog I saw in the comment section of the following blog post: James Zhan | Google De-Indexed My Entire Bear Blog and I Don’t Know Why

Only that I couldn't find the comments anymore. What!?

Turns out, as stated in the changelog of his blog, the author removed the comments section and with this, all comments.

Why!? Now all that wisdom is gone. I.. Yeah, ok. It's his blog. I get it. However I'm annoyed since I forgot to make a copy of that page in my Readeck-Instance.

*sigh* Lesson learned. I guess.

But how cool is it to have a changelog for your blog? After all it immediately answered my question.

Proxmox on LinkedIn: "IQS Barcelona, a leader in science and engineering, was locked into a costly, restrictive legacy virtualization platform."

Later in their Whitepaper they name VMware explicitly.

Well... 😆

For a few months now, I've been regularly coming back to this point where I ask myself whether I want to continue using Bludit. The latest version dates from August 2024, and there are issues with IT security-related bugs open and unresolved on GitHub.

Sure, Bludit is open source. Anyone can fork it. But Jürgen Greuter (alias: Tante) wrote back in 2013: "Host your own is cynical". In this text, he discusses why not everyone can set up and operate software "just like that" when a service is discontinued or its business model changes fundamentally.

And in this sense, I would like to note: "Fork your own is cynical"

I want to blog. I want to write down and publish my thoughts. I don't want to programme PHP or deal with problems in dozens of different browser versions. In some cases, I would also have to acquire a lot of knowledge (again) first. And the time spent for maintaining the fork? No, thank you.

I just want to be a user. Period.

And well, as can be read in the Bludit forum, the only developer (Diego) is not working on Bludit until further notice. There are apparently only minimal adjustments. Too bad. Also because security-related bugs are obviously not included.

But just as I simply want to be a user, I can understand that Diego also has a life and needs to pay his bills.

So I did a little research and came across the blogging software Kirby. Also a FlatFile CMS. You do have to buy a licence for Kirby, but at 99€ for three years, it's more than fair. And the source code is available on GitHub. So if I want to, I can dig through the code myself and see what's going on or whether there's already an issue for my problem.

What's more, the software has been on the market for over 10 years and is used by several well-known magazines and projects (e.g. OBS and Katapult Magazine). That also speaks for its reliability.

Well, I think I'll spend a weekend or so with the trial version and see how Kirby feels. The demo was nice, anyway, and didn't leave me wanting anything.

HomeOffice was big during the Covid-19 pandemic. And it still is. Especially in industries where the place of performance can differ from the company's headquarters without having to fear a loss of productivity.

Ironically, these sectors were subject to numerous "return to office" (RTO) initiatives from companies that had previously praised themselves for enabling all their employees to work from home full-time. Admittedly, many of these RTO strategies were actually disguised job cuts. As, for example, not everyone who moved out of high-cost of living (HCOL) areas can or is willing to move back.

Naturally "thought-leaders" and other people voice opinions on why work-from-home is bad. Despite science showing the opposite pretty obvious. But recently I encountered the first argument I can understand and support completely.

It is about the training of apprentices.

The trainer said: "Normally, we would send the apprentices to various teams for six months. This allows them to learn about networks, databases and system administration for Linux and/or Windows. Some teams had to be visited as part of the training; for others, the apprentice could choose according to their own preference and desired area of specialisation. Nowadays, however, we are having problems finding teams where enough people are present each day to actually train our trainees. Training remotely is possible (§ 28 (2) BBiG (Vocational Training Act) in German law allows remote training "to a reasonable extent", not 100%), but it isn't nearly as effective. This is especially the case since many people in IT choose to isolate themselves and don't communicate proactively enough. Hence, opportunities are lost. For example, there are fewer opportunities to provide ad hoc support for complex maintenance work on failed mission-critical systems. If you are in the office, you can recognise these situations even without access rights to monitoring and can ask to sit nearby and observe or support. But remotely? Not always."

For me, this is the first genuinely compelling argument against working from home full-time.

A microwave can definitely be useful in the kitchen. I don't doubt that. Even if it does nothing more than an oven, it does it faster. However, you can't prepare all dishes with a microwave. For those, you still need an oven. I don't currently own a microwave and gave mine away years ago. I realised that the microwave was causing me to develop unhealthy eating habits. That's why I started cooking. My sister once gave me a wok pan for my birthday. It's by far my favourite kitchen appliance since.

Huh? You don't know what I'm talking about?

Then feel free to read this wonderful analogy written by Colin Cornaby:

In the Future All Food Will Be Cooked in a Microwave, and if You Can’t Deal With That Then You Need to Get Out of the Kitchen

Via Mastodon I learned that there is a monospaced version of the one font we all love: Comic Sans.

It's called Comic Mono, is available on GitHub: https://dtinth.github.io/comic-mono-font/ and does look somewhat good. 😆

Have fun!