I've noticed that a lot of devs tend to get annoyed and/or shrug off their stakeholders' AI code contributions. Why toss it out? Try this instead: 1. Promptly thank them for all their hard work. 2. Inform them that you trust their work and can put it right into production ASAP, as-is. No further review necessary. 3. Let them know that their contribution will be fully credited to them in version control. Stakeholders love seeing their name on stuff! 4. Request additional contact information, just in case anyone has any further questions about what they provided.

I went way too long between keyboard maintenance on my daily driver. Last night, I did a full disassembly, deep clean, and switch lube. This thing was so neglected that it might take me a few days to readjust and get up to full speed again.

Last week, I came across what might now be the rarest game in my home arcade collection. Former owner was an operator back in the day and reached out. This one was sitting in his house, stopped working, and asked if we wanted it. Today, I popped the locks. More info soon...

Got that @DRxRedacted playmat still on my mind. Questions for the murder surgeon: - Permission to "fair use" a pic for my own personal playmat? - You want one too? If you're up for it, a photo with a MTG card stuck like a forehead gusset might be dope AF.

Had a thought while playing MTG on Friday night: I need a @DRxRedacted playmat in my life.

Nothing quite gets the blood pumping like a Pyrenees suddenly going full-on "fuck shit up mode" in the middle of the night. False alarm, but good job, Moro. ❤️

PSA: it is your civic duty to notify @xojessfrick of each and every @Canes win. Bonus points if you do it for every goal.

We cooking.

The WordPress community had has a lot of thoughts about Emdash. Here's mine: The most important thing to know: it's a CMS layer on top of Astro. What does that matter? 2 reasons: 1. At it's core, it's not something super new and unstable. Astro is incredibly mature and well maintained. 2. Emdash takes something that was built for modern developers, with a ton of great conveniences, and builds something accessible to WYSIWYG folks on top of it. I've been using Astro to build sites since the pre-1.0 days. Back then, it was primarily for static content. As it's evolved, it's gone from being a really great SSG to my go-to framework. IIRC, one of the first ones I put into production was the Pagely Quickstart docs site. Yup, I decided against using WordPress for an enterprise WordPress hosting company's docs site. Why? Astro was the better tool for the job. I won't go into all of those details right now, but building and maintaining it in WordPress would have been a PITA. I needed fast, reliable DX with near-zero maintenance. But here's the problem with Astro: if ya can't write up some code, Astro is gonna be a bad time. It's a framework, not a CMS. WordPress shines because of the WYSIWYG nature of it. Even your mom can write a blog post in WordPress (she told me in bed last night). If she needs something extra, there's a rich ecosystem of plugins and themes to go wild with. Worst case, she hires a dev to build something custom - WordPress devs far outweigh the demand. Emdash is to Astro was the WordPress admin dash + post editor is to WordPress core. But here's the big elephant in the room: is Emdash the "WordPress killer" that it's claimed to be? Short answer: Ehhhhh... Right now? Not really. Long answer: Over time, quite possibly. But that's going to depend on a lot of variables. 1. WordPress isn't going anywhere, even if market shifts. We still have demand for COBOL devs, we'll still have demand for WordPress devs for years to come. Companies take an eternity to switch over things that already work fine. 2. The WordPress ecosystem is so huge that it's going to be a while before anyone has 1:1 solutions for all the weird niche stuff. Especially if we're talking about non-devs who need a site builder experience. 3. WordPress could start progressing. If the repo got cleaned up, dev workflows improved, hosting became reliable, and WordPress people stopped being "WordPress people", WordPress could regain the community hype that it used to have. Anyways, there's my brain dump. If you have thoughts, hit me with 'em. TLDR: No, Emdash isn't going to murder WordPress. At least not right now. But it has a ton of potential. Only time will tell.

SO STOKED FOR THIS MATCH!

I was just thinking: It's pretty dope getting to work on a tech product/team, for a low-tech industry, with folks who have taken such drastically different journeys to get there. Over the last 15 years or so, I've worked for tech companies. Specifically, tech companies in the open source space. What happens when you work for FOSS-driven tech companies? You mostly work with a bunch of nerds who share that same passion. Everyone's open source habits just become normal, everyday expectations. For example: - If your PR doesn't even pass linter checks, don't even bother. - Prepare to have every line you write mercilessly critiqued by countless people, for all of eternity. - If something could have been done differently, you're gonna hear about it. - If someone took the time to mercilessly critique your work, it's usually because they care. Rejecting and closing is way easier. - Spending countless hours reading, modifying, critiquing, and openly collaborating on things that have an infinite number of possible solutions. - Industry trends like languages, frameworks, libraries, patterns, etc. are common knowledge and on everyone's radar. - It's more common than not for people to have side/passion projects that they either maintain or contribute to. In that little bubble, it makes perfect sense; it's magical. Outside of that bubble, where people's tech jobs are just jobs, I'm definitely the weirdo. At some point, I forgot that. Or maybe I never learned it to begin with. Either way, I've been taking time to learn and grow. Recently, I've learned a lot. To name a few: Lesson 1: Not everyone spends time outside of their 9-5, tinkering around with the new hotness. Most probably don't even care; what they have works fine. It only matters when it matters. Lesson 2: Some people aren't used to the whole "critique it to death" lifecycle. Explicitly ask for the kind of feedback I want. Be patient when supplying it. Lesson 3: Many folks in non-technical roles don't know "how the sausage is made" or even care. They have no interest or practical reason to. It might not even matter if the sausage is good - it just has to be edible. The thing I keep reminding myself is that it's all contextual. Situationally, they go in any direction. They're just different perspectives; influenced by different career paths and experience. Overall, it's been a been a super dope experience. Once it all clicked, I started really enjoying this new challenge of learning more about myself, others, and how it all fits together. Anyways, I didn't mean for this to be a whole-ass page full of ramblings, but I wanted to share. If you got this far, congrats. I hope it was worth it. 😂

NEW CHAMP! Hell yes you deserve it @DRxRedacted #NHB97

Just finished #NHBPit. Awesome little shitshow to lead up to #NHB97. Loved it. Fuck yeah let's fucking go.

Every time you use a single-letter variable, God kills a kitten. Have mercy. Please think of the kittens.

Hey @AnkerOfficial/@soundcoreaudio support folks: Any issue with leaving my Anker Sleep A30 (or my older A20) case plugged in all the time? Any battery degradation or other issues with that?

Hilarious *and* useful?! Yes please. github.com/PeonPing/peon-pin…

It's here! Guess what we're doing this weekend!? #ResidentEvilRequiem