I just told this to my wife, and she giggled.

I’ve got a DELL server that I used as home server, but it was too loud. But it worked well, even at an advanced age. I moved the disks to a normal desktop machine (not DELL) that is much, much quieter.

If you don’t put the answer in the title, it’s clickbait, nothing more.

For small niches, six months can be rather aprupt.

While it is good not to waste hardware, maybe you should grab the opportunity now that the windows addicts have to upgrade their hardware to “follow the light”. They usually throw out boxes with bigger chips than a Pentium M.

I hope the stickers are just a prototype thing…

Apt update and upgrade happen automatically.

Forgot about that website you visited 3 weeks ago, late in the evening while drunk? Yup, we stored that!

Yes, but the search engine is so crappy you won’t ever find it. Our AI is thankful for the input, nonetheless…

My wife is the last one in the family to switch to Linux. I started with Linux on PCs (I only used Windows 95 back then in a dual-boot config for gaming only, but did work on Linux back then already), my daughter and my so use Linux for University, and now my wife is the last one to convert over the Win11 fuckup.

Linux server administration tool, web interface based. Makes managing servers way easier.

I just repurposed one of our older PCs for that task. Slap Ubuntu on it, install webmin, and you’re set up.

Yes, but a lot of ZigBee stuff ends up in environments that use a cloud-connected “smart” hub.

That’s why I never went serious into home automation. Because any affordable system is based on cloud shit beyond my control. Cloud goes belly-up, and thousands invested ins such a system are suddenly scrap? Not with me.

If they have one.

This could be vibe coding, or just an intern “doing the web site”.

Neither should have write access to production code.

First of all, like all skills, the more you do, the better you get.

One approach not listed would be to read books on algorithms and try to implement them.

Another would be to read good source code. The “good” part is the difficult one here, though.

Have a look at “The TeX Book” and/or “The MetaFont Book” - Both books are well annotated “sources” for two working and long-term assumed bug-free programs. You can learn a lot from those, not only about actually writing a program, but you can get a lot meta-knowledge off this project.

Or look at the sources for the glibc/glibc++.

If he mentions it, one has to assume that he knows enough about it to lie.

The ultimate red flag. They probably lie about paying you, too.

Speedy recovery, and all the best!

OK, I have not played it for AGES. Nice to see something like that fixed, as it was a bit system-inherent.