I started a newsletter! I wanted a place to write medium-length content that was less ephemeral than a tweet but more conversational than a blog. I’ll cover everything from web dev and nerd stuff to family and culture. I’d be honored if you subscribed: onlygoodtakes.com

Had some Canadian business partners fly down and the thing that blew them away was hospital billboards showing live-updated wait times at their emergency room. They were like “7 minutes?!?!”

Elon could literally solve homelessness tomorrow. All he needs to do is sell his stake in the companies he created from the ground up, crashing the price and evaporating his wealth as well as the savings and pensions of workers globally.. handing the control of these companies over to short term profit interests and preventing any long term vision from being enacted.. THEN take whatever money that remains which will be nowhere near 1tn and give it to homeless charities who have never solved homelessness anywhere on earth because they’re financially incentivised to do the opposite. Bam - homelessness solved. The reason he doesn’t do any of this is because he’s evil.

Local compute starting to be an issue for my coding throughput

up your flirting game, y’all yeah, 'cause calendars is players too

LOL the USA World Cup goal sniper literally has “gun” in his name 🦅🔫⚽️🥅

See you in the desert, friends.

There, we got rid of one today

Has anyone found a way to make your agent skills self-healing? Sometimes I’ll find that some command no longer works or a URL changed. And the agent figures it out, but has to misstep every time. So I go and ask for it to fix the skill. But what if it could just see the deficiency and kick off a subagent to fix it for the next run, automatically? Way to do that without too much context bloat? Better to just have a “refine-skills” skill you run when you see a skill making an agent step on a rake?

Git worktrees are simple. 1. DB: a .git directory containing your objects, commit DAG, refs, etc. 2. Worktree: a HEAD, an index (staging area), and a checked-out view of a commit. Normally those live in the same directory. But what if they didn’t? One DB, multiple worktrees.

Some random ER doc in Raleigh did an amazing job on these stitches

I love when @sarcasmically can't get the Spelling Bee pangram. She was like "Is it Towelini!?"

She doesn’t even try to make an argument for why this will help anyone. It’s just “demand for AI is growing, let me extract my toll” *If* data centers are causing electricity costs to go up, just charge them the true marginal cost or require them to make their own power.

Spent a couple hours playing this with my teens tonight and legit my new favorite couch game. Spiders with guns and lightsabers with physics-based webslinging and platforming. So much fun: spiderheck.com/

Considering whether OpenClaw and Obsidian bases would be a good solution for doing office inventory, I have a lot of stuff in here that is reasonably organized with SKADIS and Gridfinity plus some deeper storage, but I don't always know exactly the location of a specific item.

This is actually a great idea. You learn so much about someone be seeing how they handle “boring” chores. And you can converse, and it’s free. And she gets to talk to you about her passion.

Me: So the trip is four days. Underwear. One. Two. Three. Four… Brain: No Me: But— Brain: NO Me: Ok Brain: Thank you Me: And five in case— Brain: NOOOOOOO Me: —I shit my pants