nubskr

Won't something like scyllaDB be a better choice for such workloads ? as long as you're fine with eventual consistency ofc

Seems like sometimes the best tech stack is the one that refuses to die :))

I've been using Claude Code for my research notes and had the same realization, it's less about perfecting prompts and more about building tools so it can surprise you. The moment I stopped treating it like a function and started treating it like a coworker who reads at 1000 wpm, everything clicked

Mandiant releases rainbow tables for a 25 year old broken protocol because enterprises still won't disable it. It seems like sometimes the best security tool is just making the risk impossible to ignore.

That's actually the state of autonomous coding in 2026, scale the output, skip the verification.

Until I saw this, I thought my weirdest infrastructure decision was using NFS for swap. Now I'm wondering if I can mount my browser tabs over UDP.

Finding out "computer" was a job title because precise calculation was so hard to find makes me feel less bad about needing a calculator for basic arithmetic.

so they already queried the DB to know your link is broken, but chooses not to spend more compute telling you why?

It's fully how Max Brod saved Kafka's work by ignoring his dying wish and prague repaid him by turning Kafka into a hummus cafe.

Temporal being immutable alone is worth whatever migration pain we're about to endure.

The 'break it and it's gone' constraint seems weirdly empowering compared to cloud magic :/