Prateek

Omacon 2026 attendee.

Views are my own.

[Ryan Petersen @typesfast]

8% of the air freight entering the US from Asia is components for data centers.

30 full freighters per day just in chartered volume, a lot more shipping less than plane loads at a time.

[tobi lutke @tobi]

Our house in Toronto had this fancy glassed wine cellar, but we are not big wine drinkers.

Anyways, it had good climate control so here is my rack cellar.

[dax @thdxr]

people working on agents wish they were ai researchers

people working on regular products wish they were working on agents

so they all create a ton of noise when they should just be focused on the space they're actually in

[Naval @naval]

AI isn’t going away. Barring unprecedented global government coordination, it isn’t even slowing down.

The only real decision is whether to centralize power, or disperse it.

Do you fear the technology? Or a small number of people controlling the technology?

[International Space Station @Space_Station]

.@NASA astronaut Jonny Kim retires from the agency after nearly 10 years and one mission aboard the International Space Station. He will serve as lieutenant commander in the @USNavy. More... https://t.co/YSES3amIN5

[tobi lutke @tobi]

@k_flowstate its the year of linux

[Andreas Kling @awesomekling]

>code is slow
>ask agent if it’s one big bottleneck or death by a thousand cuts
>it doesn’t understand
>pull out illustrated diagram explaining one big bottleneck vs death by a thousand cuts
>it laughs and says “it’s one big bottleneck sir”
>look at profile myself
>it’s death by a thousand cuts

[tobi lutke @tobi]

@chandrxn Find something that exists that inspires you and chip in. If nothing inspires you, start something that would. Find others like this. Repeat until career is done.

[Guillermo Rauch @rauchg]

If you’re not reading the code, whether explicitly or through agentic inquiry, one or more of these is true:

○ You’re a beginner
○ Software is throwaway
○ You’re prototyping
○ You have no users / revenue
○ You’re taking on debt & risk
○ Your problems are basic

And btw. All of this is fine. But the reality is that models are still not at the “full autonomy” stage yet.

They make rookie mistakes, they go down bad architectural paths. I just had the best model in the world add a nonsensical 700ms delay to “settle” something and it told me “you’re right, I was cargo-culting” 🤨

I am on the camp that this need will diminish more and more. Most code is indeed going to be assembly-like. But we also have the global internet and software infrastructure riding on these models and narrative, and we have to respect that.

[Denny’s @DennysDiner]

@JensenHuang @nvidia

[almonk @almonk]

https://t.co/Rz0q1W33ut

[Jonathan Blow @Jonathan_Blow]

At Whole Foods, avoiding the Oat Milk and Gluten Free products is like trying not to step on landmines.

I accidentally bought non-dairy cookie dough once. Never again.

[Mitchell Hashimoto @mitchellh]

Mind boggling to me that I can make a thing faster and there's always people that ask "but why?" What kind of mentality is that? The pursuit of excellence does not need justification. Also, I find in so many cases, we can't know the impact of an improvement until we do it.

For example, one I've talked about before: Ghostty's high IO throughput has enabled terminal program (emulator and TUI) fuzzing at a speed thats incomparably fast to prior solutions. This has resulted in upstream patches to resolve issues in popular projects like btop, tmux, and more.

Speed enabled that anecdotally example that lifted the tides of adjacent communities that don't rely on Ghostty technology at all. I didn't predict this.

Make things better because they can be better and let the results naturally play out.

[Andreas Kling @awesomekling]

A lot of programmers are basically fans of programming itself. It’s all about them. They have mastered Rust or Haskell or Zig or whatever, but their objects of veneration are useful mainly as a backdrop to their own cleverness. Anyone who will spend six weeks rewriting a working system in a new language to make the types nicer is more into the rewrite than the product. Extreme technical obsession may serve as a security blanket. If you are the person who knows every flaw in the architecture, every impure abstraction, every place where the old code fails to express its true intent, you already know what to say in every meeting, which is so much safer than asking whether users care.

Your obsession with refactoring is your beard. If you know absolutely all the trivia about borrow checkers, effect systems, async runtimes, and build tools, it saves you from having to know anything about customers, deadlines, support, sales, documentation, or whether the thing actually helps anyone. That’s why it’s excruciatingly boring to talk to such people: they’re always asking you questions they know the answer to, and never shipping anything that answers a question users actually asked.

[Noctua @Noctua_at]

Available now! With first-class cooling performance, superb quietness of operation and industry-leading reliability, our new NL-LC1 series brings classic Noctua virtues to the world of all-in-one liquid cooling: https://t.co/9KJREnY3rC

[The White House @WhiteHouse]

Just the beginning of a legendary night at the People’s House. 📸🇺🇸

[U.S. Air Force @usairforce]

What’s better than a rare Super Delta formation featuring the Thunderbirds and the @USNavy Blue Angels over Washington, D.C.?

Watching it from four different views for #UFCWhiteHouse as part of #Freedom250. 🇺🇸

[Mitchell Hashimoto @mitchellh]

I've got an agent in a loop optimizing a renderer with the goal to minimize frame times (and tests to measure). It got times down from 88ms to 2ms and allocations down from ~150K to 500. Sounds good, right? Wrong. This is exactly why agent psychosis is a big fucking problem.

As an experiment, I rewrote the Ghostty core render state in Go, with access to identically laid out data structures as Ghostty and the exact same validation tests. I made a purposely naive renderer (simple, correct, but slow). 88ms per frame with 150,000 allocations (horrendous, lol)!

I then kickstarted a Ralph loop to bring the frame times down. I told it it can't modify input data structures or the public API or tests (they're correct), but it can do anything else it wants. It got to work.

It has worked for about 4 hours. I've spent around $350 on this experiment so far. The results?

88ms => 1.5ms
150K allocs => ~500 allocs

Incredible right? Nope.

My hand-written renderer I ported has frame times (same benchmark) of ~20us (0.020ms) and 0 allocations in the update path.

This is the problem with psychosis and lacking systems understanding. If you don't understand the system, you're going to accept that this is an incredible result. If you understand the system, you'll see better solutions immediately and can do roughly 75x better on throughput.

The people who blindly trust agent output are in the former camp. They're sheeple, overdrinking from a fountain of mediocrity.

Standard disclaimer: I use AI all the time. I like AI. The point I'm making is to not blindly accept results. Think. Analyze. Learn.

[Mitchell Hashimoto @mitchellh]

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.

[dax @thdxr]

we're going to hit 1M daily active users in the next few weeks

the whole way here almost all the thought leaders kept explaining how what we were doing was wrong, bad taste, wouldn't work, etc

none of them were curious enough to ask us what they got wrong