Same here! I remember when Digg only supported single-level replies. Good times...
Cratermaker
I had one of those that was grandma-owned but the transmission shit the bed within 5k miles. What a pos.
I understood what he was talking about instantly... but only because I did the same thing with the brake when I was a kid.
I had a viscous reaction, if ya know what I mean.
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.
The Navidson Record from House of Leaves, although it's questionable whether it is supposed to actually exist within the narrative.
3Blue1Brown on youtube has amazingly good visual explanations for various math concepts. Helped me out a lot when I was having trouble with calculus. It doesn't help specifically with memorizing theorems or anything, but provides a good conceptual framework to start with. https://www.youtube.com/c/3blue1brown
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 probably got stuff done, just not the things you left half implemented code for...
I hit the "wake on lan" icon on my phone, since my computer is in a different room from my monitor and the usb doesn't work for waking it up directly. But if I could, left ctrl all day!
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.
I think what started me down the anti-React path was realizing that there were other frameworks out there that don't even use a virtual dom. Plus you get tired of being told that the most obvious and intuitive way to do various things in React actually goes against some best practice that they've established.