I'm an engineer @OpenAI. Author of @octanejs, @ripple_ts, @lexicaljs and @inferno_js. I was also a core engineer who helped build @reactjs and @sveltejs
hi all, two things:
1. usage limits are back to being double – your feedback worked
2. we today kicked off an intense sprint to dramatically improve the app simplicity and performance. i will oversee this. more to come.
now, send me your complaints
Goose: my latest programming language. Safer, faster and less memory than Rust/C++ for algorithms where tightly packed, flat data structures matter.
It can represent more kinds of data structures as flat, pointer-free bytes than any language I know.
github.com/aardappel/goose
1/
I think there’s still a big difference in human vs AI slop.
One tends to be illogical and the other is logical but the wrong path. Humans take paths to exploring problems.
With specifically LLM AI, it just does what it thinks is best reward worthy to resolving the problem needed to give the best token output. You could say that it’s like a human cutting corners, but the best engineers never do that.
Humans reward peer feedback and getting better and getting a promotion, or not getting sacked. If LLMs had that mentality then maybe we’d have less slop.
it's very interesting how many replies i've gotten about maintainability and clean code being still important. i would argue that that is no longer true and we all need to update our priors on what Good Code really means in 2026.
clean code has always come at a cost - performance. indirection and making code readable/understandable for a human is not free, it often comes at the cost of worse performance. we have historically been okay with this because of Moore's Law and the fact that most code is not on the hot path.
these principles also came from a time where humans maintained code. it made sense to optimize for humans then, but it makes less sense now when agents are already writing all the code. we will in fact probably discover and come up with new principles: principles of agent friendly architecture (i plan to write more thoughts about this soon)
TSRX usage has grown by almost 2x in the last month. Which means we’re soon to be eligible to be included in Linguist - the code highlighter for GitHub!
We’re also close to having TS 7.1 support, a major stepping stone towards TSRX 1.0
I can’t disagree with this more. Software engineers might not write the code anymore, but there is definitely a bar in terms of quality.
You either ignore it in review because you don’t think it matters or you don’t understand the changes.
We’re not there yet in terms of that cycle.
Best part of AI is shattering dev's egos, the worst part of this industry.
You are not special. Your code actually sucked like everybody else's. You were never the smartest person.
The things my sales guy BIL and designer brother are doing is beyond anything I have done.
Strongly agree here that when we get this right we will unlock some truly incredible patterns and performance wins. Streaming async signals from first paint to pre hydration to post hydration is a huge unlock.
The irony is that Octane now has its own signals implementation that strives to do server-side streamed signals, avoiding hydration and pathing a way to even more peformant patterns. We'll be sharing more about this soon.
I can't believe it has taken me this long to get to read this absolute gem of a discussion between @RyanCarniato and @trueadm
while most folks are still stuck on "use react because it's in the weights", both ryan and dom are as usual uncovering the frontiers of modern tooling for agentic engineering
i've still only read the summary, can't wait to dig into the full discussion
gist.github.com/aleclarson/0…
new post: the senior engineer death spiral
sunilpai.dev/posts/the-senio…
a friend just started a big job and asked for some advice. so I braindumped a monologue about a super common failure mode I see with engineers and posted it here, hope it helps whoever it can.
As we prepare TSRX for 1.0, we’ve decided to remove “lazy destructuring”.
This reflects the direction we want to take TSRX: an extension of JSX, rather than an entirely new language.
We’ve written more about the reasoning behind the change here:
tsrx.dev/blog/removing-lazy-…
Thanks for asking! I have an internal bench and @octanejs is already ahead on js-framework.
Yet @trueadm and I think it's far its ceiling: instead of using the universal renderer, we should compile specifically for Lynx.
Codex on it. Stay tuned!
Martin Ødegaard this season so far :
- mØtm vs Man City
- mØtm vs Coventry City
- mØtm vs Chelsea
- mØtm vs Napoli
4 goals in 5 games. Returned sharp and fit from the World Cup. He was sensational tonight again. Scored some top goals this season. BravØ. @OnlyWilo_ 👌🏽
I asked GPT-6 Astra to mine a diamond in Minecraft using computer use, then went to sleep.
Woke up to a diamond in its inventory 🤯🤯🤯
Setup in the replies.