The major lift.

I mean, is it a wool sock? I feel like that’s relevant.

A guy I was dating noticed the anti-dandruff shampoo in my shower. Perplexed, he asked me “Why do you have anti-dandruff shampoo? You don’t even have dandruff.”

I responded, “Exactly.”

He did not get it. I had to explain.

Not so much a tear as it is a rip. And not so much fabric as it is dry wall. But the point remains.

Does the Steam Deck count as Linux Gaming? I assume it does, but honestly in the year 2024 and on niche forums I never know.

If it does count, then I bet my gaming percent is nearly as high. I prefer the larger screen on my laptop and some games that I play don’t run (or don’t run as well) on the Deck, but otherwise everything else about the Steam Deck makes it the superior experience.

On the one hand, I’ve had a bad back since my teenage years and definitely this is a thing that’s happened to me when I was young. On the other hand, it’s a thing that’s also happened to me more than once now that I’m older, so I’m generally as cautious and careful when sneezing as I am when I feel a fart coming on while I’m dealing with diarrhea.

From what I gather, the general consensus is that Doom Eternal is the better of the two most current (at this time) Doom games. That opinion is fairly consistent from reviews and posts I’ve read.

Doom Eternal is a go-go-go-go-go never stop moving always be shooting kind of game, as far as I can tell. IIRC there are even in-game hints that pretty much say “don’t sit still”. I’m just a super casual occasional gamer, so the always under attack game play in Eternal is a bit much while I’m also grappling with learning the controls since I don’t really play first person shooters.

So for that reason, Doom is currently a better fit for me and my preferences. The game play is broken up into exploration that’s punctuated with enemy encounters. And the encounters are largely set-up so that I can take on enemies at my own pace. Slower, more calculated, gives me time to think things through and consider strategy.

Also for some reason, the gyroscopic aiming wasn’t enabled by default on the Steam Deck when I tried Doom Eternal. There are some settings I can adjust that are supposed to enable it, but I haven’t spent much time testing those out. If I can make those work for me, then I suspect I’ll have a much better experience with Eternal than I’ve had thus far.

Currently I’m playing Doom (2016).

I have had it in my Steam library for years at this point and I have tried to pick it up and play it many times in the past. My attempts to get into it never worked out.

Earlier this year I remember reading some posts comparing Doom and Doom Eternal (plus there’s been some excitement about the new Doom game in development), so based on that, I decided to give Eternal another chance. Still wasn’t getting into the game but I remembered reading suggestions that Doom is a little more laid back and more of a take it at your own pace kind of game. So, once again I fired it up, and it drew me in this time.

It really helps that this is the first time I’ve tried playing it on the Steam Deck. Not only does it run decently well on the hardware, this is the first game I’ve played that takes advantage of the gyroscopic aiming. That has vastly improved my enjoyment since it makes aiming so much easier for me and takes a lot of the frustration out of the battles for me.

I don’t get much time to game, so I probably won’t be finishing the game for awhile. After I’m done, I may give Eternal another try. Then again, I’ve been itching for some Resident Evil game play and I have several of those waiting for my attention.

I just purchased Grim Dawn this morning. It’s on deep discount and I figured it wouldn’t hurt my feelings if I didn’t get around to playing it for awhile. I haven’t started it up yet, got too many other things on my plate and several other games ahead in my queue of things I want to play.

I know that “brain damage made me conservative” is sort of a meme, but this has happened to several friends and family of mine over the years. It’s happened enough that I seriously think there’s something to it.

I doubt it will be too wet, but it will likely get too cold to reliably grow most vanilla species outdoors all year long. I think most conservative estimates say it’ll grow in zone 11 and up, so if your specific doesn’t match that criteria, you’ll probably need to grow it in a pot and grow it some place warm in the winter.

It can be grown from seed, but it’s a complicated process that will require some research and technical skills for a good chance at success. Then it will be about a decade or more before the seedlings are large enough to start blooming. Most people do not grow from seeds for this reason. It’s much easier to grow from cuttings.

If I were going to use a dye on my skin for something like this, I would first test it out on a small patch of skin some place where nobody’s ever going to see it, like on my penis.

Isn’t daylight savings time 8 months of the year? The four “winter” months are when we’re on standard time, so seems like it would be pretty easy to ignore DST during those 4 months. Or maybe I am misinterpreting?

Well, some people say men are basically just dogs and I guess if some of us can lick our own assholes, that’s further proof.

I use VS Code and GitHub Co-pilot and develop in a variety of different languages and frameworks. I’ve got lots of experience with some, but I’m less knowledgeable on others.

So, having the AI assist with languages I am very familiar with is basically a way to save time and preserve my mental energy. For languages and frameworks I’m less experienced with, it speeds things up because I’m not having to constantly search how-tos and forums for guidance. And for languages/frameworks I have limited or no experience with, it can be a helpful learning tool that speeds up how long it takes to get ramped up.

With this set-up, if I start writing a line of code and then pause for a moment, co-pilot kicks in and tries to autocomplete that line, sometimes even suggests the entire block of code. It’s really good at recognizing simple patterns and common boilerplate stuff. It’s less good at figuring out more complex stuff, though.

However, I find that if I start out by writing a comment that explains what I’m trying to accomplish, and to some degree how to accomplish it before I start writing one of those more complex blocks/lines, the AI has a much higher success rate in returning helpful, functioning code. So, basically yes, I write the comment to describe code I haven’t written, and I’ll let the AI take over from there.

This works for code, raw database queries, configuration files, and even for writing tests. I’m not an expert at building out Docker configurations for local development or configuring auto-deployment on whatever random system is being used for a project, but I can often get those things up and running just by describing in comments what I need and what I’m trying to accomplish.

The VS Code co-pilot extension also has some context menu items that let you ask questions and/or ask for suggestions, which comes in handy for some things, but for me, typing out my intentions in comments and then letting the auto-complete kick in as I’m starting a line of code is faster, more efficient, and seems to work better.

Granted, co-pilot also likes to try to auto-complete comments, so that’s sometimes funny just to read what it “thinks” I’m trying to do. And most of the time, I do remove my comments that were specifically to guide co-pilot on what I wanted it to do if they’re super redundant. And, at the end of the day, not everything co-pilot suggests is production-worthy, functional, nor does what I actually described. In fact, a lot of it is not, so you should expect to go back and fine tune things at a minimum. It’s just that overall, it’s good enough that even with all the supervision and revisions I have to make, it’s still a net positive, for now.

As a kid, by the time I started hearing about the system via video game magazines, which were kind of like miniature websites but printed on paper and then distributed via mail and stores, I was convinced it would be the next big thing. By the time it was launched, I knew it was going to be the new top dog in the industry. When I finally got my hands on one, it was (pardon the pun) game changing for me.

The system definitely had its flaws, but it was an evolutionary step up and order of magnitude bigger than anything I’d ever experienced before.

And go figure, it was the last system I owned before I stepped away from the gaming hobby for nearly 2 decades. Life, uh, got in the way.

I’m a doomy girl, in a doomy world.

What you don’t know is that he died when he was pulled into a jet engine.

Remember That DNA You Gave 23andMe?

No. When did I do that?

I know some folks are joking about and dunking on this, but in modern times, I have justification. Call me lazy, but I have found myself writing out these comments and then letting the AI take over to at least give me a sketch of an implementation. Works reasonably well and saves me a lot of time and effort. Mostly I don’t bother to remove them, though I usually edit them a bit.

On the other hand, there are factions within my colleagues who steadfastly insist that commenting is unnecessary and to some degree even potentially harmful, and that if you feel the need to comment your code, it means your code should be improved so that it’s obvious what it is doing without the need for comments.