A. retweeted
When I was writing Unreal Engine 1, my time was divided as follows:
- Around 30% went to seriously deep coding on hard problems: assembly language texture mappers, C++ BSP trees, data persistence, object oriented systems design, and networking.
- Around 70% was just typing and refactoring large bodies of code needed for a complete engine feature set. This was not hard, and while I was doing it my mind was mostly on the deeper coding topics, thinking and planning for what's next. It didn't feel much different from vibe coding today, except that it was just me typing code on an IBM Model M keyboard rather than prompting it and reviewing the results.
So, it has always seemed perfectly logical that we would rely on AI for that 70%, once the AI could do it with a similar quality standard as we could, which has never been perfection. It came as no surprise that, after a few years of AI model evolution, it was able to take the reigns on that 70% and free up programmers' time for more valuable tasks.
What's more of a surprise is the emergence of AI as a sort of insta-Carmack able to solve hard technical problems quite cleverly and often cleanly, and that it's able to reason about and work in complex 3D scenes both by operating the tools and by directly understanding the raw data files.
I abandoned assembly language in 1998 when out-of-order CPUs made much simpler C/C++ code faster, and never I missed it. If prompting through architectural documents, concept art, and design plans can transcend typing code and tweaking vertices, that will enable developers to spend their time on higher-level, higher value technical and creative tasks.
What matters is the end product, whether it's a game or an engine. Anything developers can do to try out more ideas and make better software and games faster is a win for everyone.
A. retweeted
I’ve spent a few days thinking about the Tesla Roadster reveal and landed somewhere I haven’t seen much discussion. I’m neither a Tesla fanboy nor a Tesla hater. And I couldn’t care less whether what we saw technically qualifies as a flying car. Three takeaways: (1) The risk of that live demonstration going horribly wrong was real. Almost no CEO would willingly expose their company to that kind of public humiliation for a product with so little financial upside. Elon did. (2) That willingness to attempt the seemingly impossible is what makes Tesla special. It’s also arguably Elon’s greatest contribution to America. He’s helped bring back something we’ve lost. The American spirit of chasing big scary ideas that most people think are impossible. That mindset is spreading across a new generation of founders and its long term impact on America’s future could dwarf anything Tesla ever sells. I think this is deeply underappreciated. (3) Can we just acknowledge how insanely cool that moment was? We’ve reached a strange place culturally where even extraordinary feats of human ingenuity immediately become arguments about why they don’t count. Not everything needs to be a debate. Sometimes we should just be able to stand back together and marvel at what humans are capable of. I’ve been both bullish and critical of Tesla’s ambitions over the years. But watching Elon and his team push the boundaries of what’s possible reminds me why I’m glad we have him. Whether the Roadster ever makes Tesla a dollar or impacts $TSLA stock price is almost beside the point. We need more people willing to risk failure in pursuit of things the rest of us think are impossible. Because when they succeed we all win.
In a five-server Raft cluster, a majority is 3, so any 2 servers can fail and the cluster keeps working.
A Raft follower that hears no heartbeat for the election timeout becomes a candidate, adds 1 to its term and asks for votes. A majority of the full cluster wins.
A credit rating is an estimate of relative credit risk from a third party, not a buy, sell, or hold recommendation.
Asking PostgreSQL for Read Uncommitted behaves like Read Committed. Names in the SQL standard do not always map one-to-one to an implementation
I believe the goal of digital Optimus is to leverage existing legacy tools and software, just as humans would.
A. retweeted
The Tesla Model 3 with FSD is mind-blowing. Jessica and I drove to the gym without touching the controls once. It backed out of our driveway, drove there, and backed into a parking space. It's amazing that you can buy so much future for $40k.
A. retweeted
This is why Texas will do better than your state.
There is a center of gravity forming around all the stuff @elonmusk is building between Austin and San Antonio and beyond. It's going to be the closest thing the US has to Shenzhen.
Our hourlong exploration of the tech scene in Texas in full here on X.
A database commit doesn't require every changed data page to reach disk immediately. PostgreSQL can flush the needed write-ahead log first, then redo missing changes after a crash. Source: PostgreSQL WAL docs.
For ordinary U.S. cash dividends, a purchase before the ex-date generally includes the next dividend. A purchase on or after it does not. Check the announced date and exceptions
A timeout is missing evidence, not proof of failure. Stripe APIv1 idempotency keys let retries of one operation return its stored result after execution begins. Keep the same key and parameters.
A. retweeted
it’s clear we need to retire the term vibe coding because the models now produce better architecture & way more coherent code than an average software engineer.
perhaps even better than top software engineers too because unlike a human, ai has a much much larger context window.
this ain’t vibe coding at all. it’s precision engineering.
That’s right. Tesla doesn’t need to raise money or impress venture capitalists, so I prefer they develop everything quietly until it’s ready for public release and commercial deployment.
A hash ring is placement, not the whole distributed system. Replication, hot-key control and failure handling still need their own design. Multiple virtual positions can improve load distribution
Consistent hashing maps keys and servers into the same circular space. Adding a server changes ownership of an interval, instead of reshuffling every key. Stable placement reduces cache disruption.
A. retweeted
Some interesting machine & agent Vercel traffic stats.
• Across the entire Vercel network, 58.18% traffic is bot-originated (last 30d). This was 32% in Jan 2024.
• 60%+ of deployments on Vercel are now agentic, up from ~3% in Jan 2026.
• Up to 83% of pageviews are now coming from agents to Vercel's own documentation sites. The % reliably increases the more we optimize content for them.
I expect 'direct' human internet traffic to basically become a rounding error in coming years. The web will thrive, but it will be built for and by agents.
