Cratermaker

Same here! I remember when Digg only supported single-level replies. Good times...

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.

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!

For a long time I tried, but one day I just decided to focus on the hobbies I care the most about. I dumped a lot of time into software for my career, then kept up with bass guitar practice and dirt biking. All the other hobbies are things I might pick up if I have a surplus of time, but I've accepted that I'll never go that deep into them.

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.

You can read without using your inner voice if you practice. It supposedly lets you read a lot faster, though I have my doubts about how well you retain the information. One way to do it is to think "lalalala" while reading something!

Interesting, yeah. I inherited a Blazor project though and have nothing positive to say about it really. Some of it is probably implementation, but it's a shining example of how much better it is to choose the right tool for the job, rather than reinventing the wheel. For a while I was joking about setting the whole project "ablazor" until we finally decided to go back to a React/C# ASP.NET stack. If you're thinking of using Blazor still, though, I think two fun things to look into are "linting issues with Blazor" and "Blazor slow". I've heard people praise it, but they tend to be those who consider themselves backend devs that occasionally get stuck making frontends.

Nothing wrong with being an EMT who does all those things as hobbies, unless the capitalist pigs to whom you sell your hours demand more than their fair share...

I've had many other jobs and few experiences in them have been as humbling as programming. My favorite is trying everything to fix an issue then realizing the problem is that you're pointing at the wrong database or running the wrong branch.

Yeah! I think I still have the exact same tastes as when I was a kid. I always wanted a dirt bike and now I have one, and I always wanted a fast computer with a good sound system, which I now keep relatively up to date. Maybe my kid self would be disappointed that I don't have a fast car though!