My most common typo is gti <random command> and I’m considering to alias it as rm -rf --no-preserve-root /

name your function as malloc() and see to world burn and generate bugs at factorial rate.

volatile int blackhole;
blackhole = 1;
const int X = blackhole;
const int Y = blackhole;

Compiler is forbidden to assume that X == 1 would be true. It’s also forbidden to assume that X == Y. const just means the address and/or the data at the address is read only. const volatile int* const hwreg; -> “read only volatile value at read only address hwreg”. Compiler can assume the hwreg address won’t magically change, but can’t assume the value read from that address won’t.

And you have bootstrapped an B compiler on that?

I think the difference with Dolphin is that it now emulates an extinct system(s), so it cannot possibly compete with the actual thing. They did have a close call last year, if I remember, and they pretty quickly went into “jettison all illegal shit out of the code base NOW.” -mode.

It happened to me when I was configuring IP geoblocking: Only whitelist IP ranges are allowed. That was fetched from a trusted URL. If the DNS provider just happened to not be on that list, the whitelist would become empty, blocking all IPs. Literally 100% proof firewall; not even a ping gets a pass.

Technical debt means how much work it takes to update legacy solution to a modern solution. E.g. each time a new C++ standard is used, all code written with the old standard should be checked. The work time needed to do this is paying up the technical dept.

Now, if you are lazy, and didn’t clean up the code, used the easy and sloppy solution, next time you have twice the work to be done. So the dept gets worse, if you do nothing.

I touched a piece code that was +10 years old, according to git. Should I be scared? Will my change it survive??

I had a similar debacle, when I managed to corrupt a btrfs file system to point it wouldn’t mount again…

I was preparing it to have as my main system on bare hardware. I had accidentally mounted the same block device simultaneously in the host and guest: kablamo silent corruption and all 5 hours of progress lost.^* :(

*shred the guest VM, host was ok.

On arch, UEFI boot vars are mounted at /sys/firmware/efi/efivars. It’s unwise to rm -rf them…

GameBoy Color with a single game: Pokémon Red.

Next time I was able go to the shop they had upgraded to GameBoy Advance and no GB/GBC games were to be never found again. It was the best/worst thing I ever got. :'(

Me:

• Need to debug a program
• Debugger doesn’t work
• Need to debug the debugger
• …
• Look at a hardware bug in the CPU that breaks ptrace syscall /s
• Go find a bucket of sand.

It gets more cursed the more you look at it:

• you have to convert the coordinate axes (swap z,x,y)
• then you find out the right/left handed is flipped
• now your brain melts if you even try think how to solve this with transformation/rotation, what ever.