Just told that a software update for a screen in my car takes 2 days to apply. I’m just impressed in how it can be that bad.

“Italian algebraic geometry” Why does this actually make so much sense?

It’s amazing that I basically dislike every line of code I’ve ever written after about a month of it existing

You can even run headscale if you really care.

The hypothetical one-shot disease will ruin us all

Finally the thing I’ve been telling hundreds of people. Make a cheap MRI please.

So is a Claude subscription usable yet? Or do you still just one shot your usage immediately?

6 months ago, we met a team that was remarkably well aligned with our agentic security vision. Today, we're joining forces. We've officially acquired Keypo, Inc., and its founder Dave Blumenfeld is joining us as Founding Engineer, bringing his work on secure enclaves directly into our platform.

If Opus 4.8 actually says “delicious” all the time I will lose my mind.

I seriously cannot stand how poorly built so many apps are. Trying to build a route in @Strava and it places a waypoint in France (I'm in the US) and now I can't delete it. This is a core feature of yours that you literally have to pay for. Instead we get Trainer AI that tells me "good job you rode your bike". Fix your garbage.

Can they focus a tiny bit of that energy on making the app actually fucking work?

People building SaaS claiming we’ve hit AGI will continue to be hilarious to me.

/goal from OpenAI is pretty incredible. If you set it up right and use it for the right tasks, your agents can churn out serious work. The code it’s writing is not something I’d use in production, but that’s not the point. The research it’s doing also needs further verification, but that’s not the point either. This kind of R&D work used to take me weeks. It is doing that in 30-40 (combined multi-agent) hours and tracking its decision history so I can audit it all later. It’s really cool to see this come so far. I already have found agents useful for spitballing ideas with over the last 6 months or so and helpful for writing code for the last year or so. This new capability is another step forward in usability. Super exciting!

People complain about vibe coding ruining apps recently. OGs know that @Spotify didn’t need vibe coding to make their app intolerable.

Can you filter for certain types of cars on uber? Never want to be in a Tesla anymore.

Good lord... we're on hour 14 of /goal and it's still going...

We’ve had on the order of 3 memory bugs in 6 years of TigerBeetle. None RCEs. On the other hand, our own simulators have proactively found hundreds of (devastatingly catastrophic) distributed systems correctness bugs per year. Given how hard TigerBeetle’s domain is, in terms of mission critical financial transaction processing, I’ve never for one minute believed that writing TB in a memory safe language such as say TypeScript would somehow magically (!) make any material impact compared to the 100x correctness multiplier of TigerStyle. That’s because—rather than fall for the fallacy of composition, i.e. to see distributed correctness as a language problem—TigerStyle instead takes ultimate responsibility for the “end to end” correctness of the distributed system as a whole. Per systems engineering, correctness is always a systems design problem. For example, how to build a reliable whole, (especially) out of unreliable parts, such as broken firmware, bitrot, programmer error etc. In other words, application of the end to end principle. But when you TigerStyle the design in this way, the world of systems engineering also completely opens up to you and changes how you evaluate systems languages (now things like “power to grammar ratio”, or explicitness, checked arithmetic and precision become more critical and valuable to you). Of course, it is harder to care about correctness, to take responsibility for correctness end to end. Yes, you’re forced to begin to worry about the more serious concerns, starting with the basics of static allocation, explicit limits, assertions, deterministic simulation testing and moving to more advanced topics like protocol-awareness and storage fault-tolerance. But then again, TigerStyle is such a force multiplier, that you achieve mission critical quality, and in less time and with greater velocity. If you’re tired of production issues, and if you want to “engineer your engineering”, I would encourage you to lift up your thinking to the level of systems design and end to end correctness. Start thinking about your methodology and begin embracing TigerStyle. tigerstyle.dev

Rust versus Zig in the timeline. I’m sure someone (somehow) will just make a Zig creation that does borrow checking for you (basically).