Yesterday we launched a project in collaboration with the @okcthunder: ⚡thunder.run I couldn't be more proud of how it turned out. 🏃‍♂️💨🕹

Been working with Go's template library a lot recently, this slide deck (I know right?!) has been super useful docs.google.com/presentation…

Levie’s Law of AI Psychosis: The farther away you are from the actual work the more confident you are that humans are no longer needed I like it

Read "No Silver Bullet" today for the first time. Highly recommend it. worrydream.com/refs/Brooks_1…

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out. I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really). It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely. The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture. We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying. I worry.

Here I am with all the power of frontier LLMs and I'm auto researching emacs-init-time.

When a non-parent says they’re tired at any point of their day/life

i actually don't want this "but you don't review compiler output either" meme to die. it's the perfect signal for being immediately able to ignore someone in this space.

Don’t let anyone tell you this is wrong

End of an era @ugmonk 😢 I think it's been part of my favorite t-shirt rotation for 10 years or so? 🏆🫡 (The arm pits finally wore out 🫣)

💯 I think all the vim and emacs nerds could smell this coming a mile away. We all knew the signs.

Today is our quarterly reminder that Linus gave us a completely distributed VCS, so we stored all of our repos in a single point of failure.

recommended reading. cool they are fixing things. but it's also a reason i switched away from CC. no control over the harness means having to wait for them to fix things. the model didn't change. the harness did.

when Claude already wrote like 3k lines of code and I notice an error on my prompt

$BIRD is the canary in the bubble coal mine.

Marcus Hutchins, the guy famous for stopping the WannaCry Ransomware, probably has the best take on Mythos doing vulnerability research