![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
When you are allowed into the vicinity of this kind of equipment, you should be able to identify matching shapes without circles in the first place…
When you are allowed into the vicinity of this kind of equipment, you should be able to identify matching shapes without circles in the first place…
You wouldn’t enjoy regular sand either. It’s coarse and rough and gets everywhere.
Masks don’t only protect from airborne viruses…
Oh, that makes warnings errors and does not mean “ignore errors”. I’m not too familiar with compiler flags. You could do some mental gymnastics to argue that the unused variable causes the compiler to exit and thus the code is not functioning and thus the unused variable is not a warning but an error :^)
I for my part prefer it that way. Makes sure the code stays clean and nobody can just silence the warnings and be done with it. Because why would you accept useless variables that clutter the code in production builds? Imagine coming back after some time and try to understand the code again. At least you have the guarantee the variable is used somehow and not just “hmm, what does this do? … ah, it’s unused”
Unused variable is an error which fails to compile.
Hmm, I see. The perfectionist in me would want to shed that processor load though ^^
Without any judgement: why are your servers running X11? Just because you dislike SSH’ing to them?
You forgot the package hollywood.
I finally made a full backup of my system. I guess be happy about that.
I’m a sucker for jetbrains Mono when I need a monospaced font. It just looks nice to me.
If the package comes from the repo, you can uninstall it by the same name you used to install it. If it came from a .deb file (in case of debian), you can find out how the package calls itself and use that name to uninstall. Usually the package name is quite identical to the file name. And dpkg -L
shows you which files came from the package and where they were installed.
I’m fine with config files, as long as they are where you expect them (~/.config/tool or ~/.tool). What I dislike is yet another funny config syntax because the dev couldn’t settle on an established standard. Command line syntax is ok, if you give me sensible completions.
Not a recommendation per se, but you can use any backup software as long as you can edit your live iso. For example puting the restic binary into /opt
Using the self checkout for larger shopping is ok in my book. But what sucks is using the SCO and buying an age restricted item (e.g. beer). The checkout locks down and summons an employee to verify the age and unlock the station again. If you buy age restricted items, go to the normal checkout where your greying hair is accepted as age verification!
The thing you are thinking about is called TOTP or timed one time password.