Whenever I set something up I usually make a markdown file listing the commands and steps to take. I do this as I am setting things up and familiarizing myself, so once I’m done, I have a start to finish guide.

Raw text/markdown files will be readable until the end of time.

Idk he has kinda proven himself to be an incompetent nazi on many different occasions

Nope. It was buried 300 lines into a 600 line C function.

The cherry on top was that testing at this place was all manually done on the hardware. And the “unit testing” comprised of making one off tests to prove line coverage, then throwing out the unit tests because the IDE we were using would have an aneurysm if it tried to open up existing unit tests.

I was the poor fuck tasked with writing throw away “unit testing” code for that bastard of a function. All of it was probably written before I was born.

1. Take from index 10 of the buffer, AND it with some hard-coded hex value.

2. Bit shift it by a hard-coded amount of 2

3. Do the first two steps, but with a different hard-coded index, hex value, and bit shift.

4. OR the two results.

5. Shove the result back into a buffer.

All of this is one line with no commenting or references to what the fuck this process comes from or why it is applicable. Then there was a second copy of the line, but with different hard-coded values.