I rented Superman 64 as a kid, never knowing it was a universally hated game. We had fun with the weird multiplayer mode where you fly around in weird pod things. I remember flying through the rings too. The whole game makes zero sense in hindsight.

I bet you'd spend about 14 hours a week doing all that stuff, maybe as little as 7-10. Pessimistically then it's 56 hours of work a month and optimistically it's half that. So he'd be paying you from $31.25 to $62.50 an hour, which ranges from great to ridiculous in favor of you. Personally I wouldn't do it because of the weird dynamic of living with my boss, but there could be a great deal in there for you.

I got pulled over and the cop found a 1/2 gram of pot in my car (a very small amount), which ended up with me having to do community service and take regular drug tests. I was working as a line cook at the time, but being forced to stop smoking weed gave me the push to finally apply for an entry level manufacturing position at a local company who does drug tests. Years later I still work there, but as a software engineer, and attending online college. I wouldn't quite say I'm grateful about the ass backwards drug laws and invasive drug screening, but I really can't argue that my current situation is a lot better than it was back then. Without that event, I might still be working random entry level jobs.

There's nothing quite like the unique pain of navigating an unfamiliar codebase that treats abstraction as free and lines of code in one place as expensive. It's like reading a book with only one sentence per page, how are you supposed to understand the full context of anything??

They all look like it's just a matter of time till they shred the side of your torso or take a finger.

Exshrekting

Software devs in general seem to have a hard time with balance. No comments or too many comments. Not enough abstraction or too much, overly rigid or loose coding standards, overoptimizing or underoptimizing. To be fair it is difficult to get there.

Depending on the software, you still get to think about garbage collection!

I don't speak C, but isn't this an extreme simplification of the issue? I thought memory could be abused in an almost infinite number of subtle ways outside of allocating it wrong. For example, improperly sanitized string inputs. I feel like if it were this easy, it would have been done decades ago.

E plumbus unum

Nothing like trying to make sense of code you come across and all the function parameters have unhelpful names, are not primitive types, and have no type information whatsoever. Then you get to crawl through the entire thing to make sense of it.

Originated in car culture to describe people who take Japanese economy cars and make them look like they're from The Fast And The Furious while doing nothing to improve actual performance.