David

@PratikSinhatwt “What’s stopping you from working like this”

Can your Macbook do this ?

@thsottiaux Can we get the session titles to regenerate every X turns (3 or 5)? I end up with a lot of convos titled “Planning {feature}” or “Exploring codebase” that don’t match what I end up doing.

It’s the little things that matter, what are some small papercuts you have noticed in Codex? We’ll fix as many as possible in the next week.

@signulll ambient layer? routing? Ur about to have @garrytan in ur replies with a “many such cases”

the iphone era app was a noun which loosely was a bounded surface you opened, performed an intent in, & closed. notes, reminders, clock, calendar, etc… these are all just typed buffers with light affordances around a primitive (text, time, date). the app was the price of admission cuz the os couldn’t infer intent, hold context, or act on your behalf. the icon grid was a workaround for a dumb constraint. once you have an ambient layer that knows you incl emails, calendar, location, health, finances, conversations.. the noun collapses into a verb. e.g. you don’t “open notes,” you mutter a thought & it gets routed, tagged, surfaced when relevant. you don’t “set a reminder,” the system notices the commitment in your text thread & pre stages it. time becomes contextual too (“you should leave in 12”). calendar becomes a derived view, & not an input first static surface. all of these experiences will have to be reinvented from first principles with an intelligence layer at the core not as something bolted on.

@ajambrosino Did something happen this week?

what a week

There is a joke to be made about orbital data centers and “data gravity” but I’m not smart enough to think of it right now

it is here

Sonnet 4.6 (instead of 5 bc of internal benchmarking) dropping today?

@thsottiaux tibo I really like codex but can we please fix the automations scheduling feature? Mine just runs them every single day even when set to "exclude"

Or join Codex. We operate with much of the same principles, incredibly small and efficient. We also select for being humble and incredible at building on top of each other’s successes. Unique time to join, 2026 is the year where it all takes off.

@thisismahmoud More fun to fight about it. Nothing else to do while the agents run

The TUI vs GUI debate is pointless imo. All companies will offer both and then you pick what you prefer

@signulll does that make it a cost of dying adjustment?

@asmartbear usually I agree with you, and in this case I find it very likely that you're right

Typically, people usually are probably not likely to agree on the typical definition of words like “usually,” “probably,” “likely,” and “typically.” So… when you’re being precise, don’t use “probability words.” longform.asmartbear.com/probability-wo…

@0xlelouch_ but my side project needs to be able to handle trillions of concurrent requests

People learn fancy patterns from blogs, then force-fit them into a CRUD app that needs 99.9% uptime and basic audits. Not every backend needs to look like Uber 2016.

@flaviocopes you can’t make me give them up

New rule: any domain left unused for more than 1 year gets released to the public

@garrytan maybe your writing is overrepresented in the training data

FWIW I used emdashes before AI was known to

@auralix4 @gdb Hallucinating is core to physics research. Einstein imagined riding around on light beams all day

GPT-5.2 derived a novel result in theoretical physics, showing that a type of particle interaction many physicists expected would not occur can in fact arise under specific conditions. There is great promise in the potential of AI to benefit people by accelerating science.

@samlambert a classic energy, enjoyment, nutrition stack

drinking all 3 at once of course

today's beverage stack

@r0ktech so many things

what’s stopping you from coding like this ?

@yenkel does this count as texting and driving or are they all in waymos

you think AI will allow you to work only 4 hrs? your competitors can now ship during their commute

@awscloud our love is as durable as an S3 object

Deploy some love this Valentine's Day. Share this with your favorite person. 💕

@0xlelouch_ Really nice - one addition: partition key choice matters more than people think. Bad keys = hot partitions = bottlenecks. Good keys = even distribution = actual scale. Design your keys around access patterns, not just "whatever feels natural."

Quick notes on event-driven architecture with Kafka. 1. Producers write events to a topic (append-only log). 2. Partitions give you scale, but also ordering only inside a partition. 3. Consumers read with a group id. Kafka load-balances partitions across the group. 4. Offsets are your checkpoint. Commit is done only after work is done. 5. Expect duplicates. Make handlers idempotent. Use a key, dedupe table, or upsert. 6. Add retries + DLQ for poison messages. Set timeouts. Watch consumer lag. Kafka gives throughput. But you should handle correctness! [Part of my quick notes series]