caves of qud ass anatomical feature

*rode

strava report showing 63k ish ride with 673m of elevation gain

us hanging out at the north trail gate

arnold under a bridge

rose to the top of the great trail with two people whose legs work wayyyyy better than mine.

mutual: ugh the discourse is so bad today

me (only seen tweets about gay little gnomes): yeah it's pretty rough out there

this is fine dog

https://damrnelson.github.io/github-historical-uptime/

pizza for dinner yesterday, pizza for lunch and dinner and post-hockey today. only time will tell how much pizza tomorrow brings

RubyGems Fracture Incident Report By: Richard Schneeman This document attempts to give closure to the Ruby community about the events that led to the incident, September 10-18, 2025, which I’ve named “RubyGems Fracture.” Preamble I…

RubyGems Fracture Incident Report (September 18, 2025) by ruby.social/@schneems

rubycentral.org/news/rubygem...

RubyGems Fracture Incident Report By: Richard Schneeman This document attempts to give closure to the Ruby community about the events that led to the incident, September 10-18, 2025, which I’ve named “RubyGems Fracture.” Preamble I joined Ruby Central’s Open Source Committee on October 22nd, 2025, after the GitHub access changes. I was

rubycentral.org/news/rubygems...

what even notes.zachmanson.com/copilot-edited-an-ad-int...

mostly I just can't wait to have an office that's separate from the rest of the living space

just signed the final stuff and handed over the giant novelty cheque to the lawyers for the new place. we move next week!

gate calculator showing ~7 hours average time with reasonable values for CI, QA, code review

someone who is good at systems please help me budget this. my developers are dying agileotter.blogspot.com/2026/03/pipeline-gates-p...

guess I'm painting my new office seafoam green bethmathews.substack.com/p/why-so-many-control-ro...

not seriously interested in using this, but it's one of those things where I think it's cool that you can do this, if you wanted to thoughtbot.com/blog/meet-duck-typer-you...

now u know https://andre.arko.net/2026/03/24/how-to-install-a-gem/

pushing your org to use it as much as they can is not really much less of an unserious strategy as it would be with blockchain, or nosql, or fucking ajax for that matter.

all well and good to have a more practical relationship to this tech, but where I'm seeing that break down is when organizations are pushing their teams to use it without any kind of coherent strategy. mariozechner.at/posts/2026-03-25-thought...

In-Memory in Solidus Sorry about the digression into the world of LLM's last week. I'd spent too much energy thinking about that situation (and discussing it with people) to not...

this week in Solidus

❥ the in-memory order has been merged!!! mutating orders is now faster
❥ we've dropped our more complex Rubocop config in favor of StandardRB

read a little more about the IMOU over here: skillissue.jardo.dev/archive/in-...

"The cover letter was signed by a P. Silvia in the Ministry’s correspondence division [...]" nesbitt.io/2026/03/25/the-top-10-bi...

wrote a little about what the in-memory order updater means for Solidus skillissue.jardo.dev/archive/in-memory-in-sol...

🫠

"There will also be arm wrestling."

"dress eccentrically"?

thought more about some of what i was looking at yesterday basically we have the following challenges - none of them are new i just think they're turbocharged by LLMs 1. shipping features not worth shipping: it's pretty easy to prompt a new feature into existence so naturally the bar for what ships drops. but this shouldn't be the case, it should remain high and we should think very hard about features and if they're worth it or not. do not make these decisions solo - talk to me/frank/jay. i do not believe a prototype is worth more than spending time on product thinking and understanding why we'd even build it 2. when iterating on a feature sometimes the original design is off and forces you to do something hacky. except it's no longer you, the LLM can deal with the hackiness. so our willingness to refactor the original design drops. we should fight this - leave the code better than you found it 3. we need to spend more time cleaning things up. LLMs keep pulling us to ship the next feature but there's 100x more value in fixing what we have and improving our process of how we build things the worst part about all of this is i don't think we're even trading all this off to move faster. i think we're moving at a normal pace every team is probably dealing with this right now because we went from barely using coding agents to using them for every minor change in the past 6 months and i think they've eroded our ability to delay gratification so we need to find some balance

https://x.com/thdxr/status/2031377117007454421

that's a very neat trick https://www.joshwcomeau.com/css/header-blockers/

the only canadians vacationing in the US are driftwood www.timescolonist.com/local-news/landmark-west...

I have so many metadatas andycroll.com/ruby/handle-uncountable-...

I'm shocked newsletter.pragmaticengineer.com/p/are-ai-agents-actually...