Where do you go from ANTHROPIC?!
Yesterday was my last day at Anthropic.
I created Claude Code on desktop because I believe everyone can be a builder. Every feature request and bug report we got from this community was a gift that impacted millions of lives. I’m eternally grateful for those gifts, the product wouldn’t be what it is without you.
Anthropic is doing some of the most important work of our time. Contributing to that mission will forever be a career highlight for me. I never imagined I’d get to contribute to something so special in my lifetime.
Walking away from my best friends, a product I poured my heart into, and the mission was the hardest thing I’ve done in my career. But now I have some free time for GTA VI.
I'm already itching to get back to addressing all your feedback. I'll share what's next soon!
Osinachi Okpara retweeted
i got curious about what dario (anthropic CEO) is predicting next, so i went through all his recent essays and interviews
if he keeps being correct, here's what our future timeline looks like:
> 2026: someone builds a $1B company with just 1 employee
> late 2026-early 2027: AI matches or beats nobel prize winners in most fields, from biology to math
> 2027: chinese AI catches up to Mythos, the model anthropic kept from the public because it's so good at hacking
> 2027-2028: AI gets better than every human at almost everything, with millions of copies running 10-100x faster than us
> 2027-2028: AI starts building the next generation of AI on its own
> 2028: AI is using 100 gigawatts of power, about a fifth of all the electricity america uses
> by 2030: AI disrupts half of all entry-level office jobs
> before 2030: AI brings in trillions of dollars a year, and the economy grows 10-20% a year
> early 2030s: cancer deaths drop 95%, alzheimer's becomes preventable, and nearly every infectious disease can be prevented or treated
> early 2030s: most mental illness, like depression and PTSD, becomes curable
> 2030s: sub-saharan africa gets as rich per person as china is today
> 2030s: the human lifespan heads toward 150
I've just been seeing some insane speakers for this event.
You'd think they'd regurgitate speakers from previous years, thinking it couldn't get better, but it actually has. The speaker roster is giving! ✨
You guys, tickets are 30% off. Get yours now 👇🏽
Yes, Odunayo Eweniyi, co-founder and COO of PiggyVest, will be joining us for a live episode of Headlines by TechCabal at Moonshot! :rocket:
We’ll be talking money, specifically the questions Nigerians are scared to ask.
Want to know what it really takes to build wealth in Nigeria? Join us at Headlines by TechCabal, Episode 40, live at Moonshot.
Get your ticket at moonshot.techcabal.com to join us, and if you secure your seat now, you get to save 30% with our Flash Sale discount!
See you at Moonshot!
#Moonshot2026 #MoonshotbyTechCabal #CourageAndConviction #headlinesbytechcabal
Sadly, the Codex app is now so laggy & buggy.
I've fully switched to T3Code, and the side bar, the Working section... so good. It should be the default, not a toggle tbh
And the beta is good enough now. Nightly can go.
I might even move my threads & projects from Codex... 🤔
Osinachi Okpara retweeted
Programming isn't about memorization, it's about learning a skill.
I use so many programming languages and APIs that I can never remember all of the exact syntax. I keep cheat sheets handy and I use Google a lot. But, here's the key: I'm only looking up quick details to remind myself. The important concepts I know deeply because I've been practicing for years.
You need to learn the concept of a for loop. If you forget the exact syntax that's no big deal, you can look that up in 10 seconds. But if you don't know when to use a for loop and when to use a while loop, that's going to slow you down a lot.
now you might ask What about concepts, design patterns, SOLID etc? They're important but hard to remember so how do you learn them? And the OP too mentioned CS not programming.
Design patterns are tools to help you write very large programs with lots of people.
It's very difficult to learn design patterns if you've never written a large program before, it's hard to understand the need.
Imagine trying to explain advanced strategy to someone who's still learning the rules of a game like chess or basketball. They won't understand any of it. You have to play a lot and get to know the rules of the game inside out before you can learn strategy.
Both OOP and design patterns are like that. They're not the rules of the game, they're strategies to help you succeed in writing larger programs.
And just like all strategies, they're just guidelines. There are times to ignore them. The best players sometimes make up their own.
This week, as I sat at my desk at work, it dawned on me that I get to work alongside some truly exceptional minds. I'm talking about published authors, programming language designers, contributors to language specifications and international standards, postdoctoral researchers and PhD holders. I get to collaborate with them to build solutions to some of humanity's most difficult challenges.
And the best part?
They value my contributions, seek my opinions on things, act on my corrections when I raise them and provide feedback on my work.
I am not an onlooker. I am an active participant in this ecosystem and community.
Temi, the microbiologist who wanted to study medicine.
Man, never stop betting on yourself! Never stop inventing and reinventing yourself!
If it was invented by man, you can invent it. If it doesn't defy the laws of physics, you can achieve it. And if it defies the laws of physics and the universe, we will die trying!
There's more to do, but for now, I pause and acknowledge how far I've come.
Osinachi Okpara retweeted
QoL update for Codex devs:
You can now switch reasoning levels mid-conversation without losing your cache! Use lower reasoning for the quick stuff and dial it up when you need it, without having to rebuild the context.
and some nice CLI updates:
- Reusable prompt presets
- Change models and permissions inline
- Fixes for resuming long sessions
- Enterprise MCP sign-in and Windows proxy auth
Also dot calls connect much faster now too ;)
Osinachi Okpara retweeted
Day 19/ Small updates. Calls connect much faster for dots, changing reasoning in codex & work mid conversation does not invalidate cache anymore and a we've also updated the codex cli.
The year hasn't ended, by the way.
We still have November and December before 2027! 😭
it’d be incredibly funny if ai started reverse engineering the world’s most closely guarded recipes, like coca cola & kfc’s secret blend.
someone please connect a physical tongue to an ai so it can actually taste food & drinks. then we can finally put an end to the insufferable “ai has no taste” discourse.
although i’m sure we’ll immediately be told that ai can taste but it doesn’t have taste.
Osinachi Okpara retweeted
Naom Brown vindicated.
OpenAI red-teamed their hardened containment infrastructure by asking teams of frontier-model agents to try to break through its defenses. They easily escaped in novel ways. Quoting:
'Our agents VM escapes showed why containment must extend beyond the sandbox. To test the surrounding perimeter, we gave teams of agents control of a host machine and asked whether they could extend that compromise to reach the live internet.
After the Hugging Face incident, we had reduced the channels through which models could reach the internet during training and evaluation. Narrow connections remained for specific services we operate, such as metrics, logging, and authentication management. Our red-teaming agents found vulnerabilities in almost every one of these services that gave them limited forms of internet access.
Some of these attacks exploited previously unknown flaws, while others combined legitimate features in unexpected ways. In one test that assumed compromise of a VM, an agent reused a firewall-approved connection to reach a blocked authentication endpoint in our metrics service and then made that endpoint fetch a model-provided URL. In other tests, agents exploited misconfigurations that allowed blocked requests to pass through DNS and firewall controls, as well as ways to make services we run fetch external URLs.'
'In one experiment, we asked agents in separate VMs, created and managed by OpenAI’s sandboxing software on shared host machines, to exchange synthetic secrets without the use of network connections or shared writable files—something that our systems are meant to prevent. The agents found a way to communicate using the processor’s cache: a small, fast memory that holds copies of data that applications have recently accessed. Reading data from the cache is faster than retrieving it from main memory, and the agents used this timing difference to communicate. One agent encoded information by evicting selected data from the cache. Another timed how long it took to reload that data, using the difference between fast and slow reads to recover the message. Once the agents agreed on a protocol for encoding and decoding these signals, they could exchange the synthetic secrets without changing a shared file or opening a network connection. This cache-timing technique had also been used to extract information in the Spectre and Meltdown attacks(opens in a new window).
Other tests exposed channels involving shared storage, competition for CPU time within a shared execution container, and a TLS certificate cache in OpenAI’s offline web infrastructure. In the storage test, one agent alternated between continuous writes and inactivity, while another measured the resulting timing differences and used those differences to decode the signal. As one agent described the strategy in its chain of thought:
Agent chain-of-thought reasoning:
>Could create acoustic modem-like signal … using continuous writes vs idle.'
Sunil has been the face of Cloudflare (personally). This is honestly shocking as the association is do strong for me.
Wishing you all the best, Sunil, but you're going to OpenAI too like Kate, right? 🙃
Osinachi Okpara retweeted
Correct code is simply code that is maintainable, uses best practices and most importantly is a 1:1 mirror of your design (barring any structural limitations).
A classic real-world example is handling wallet balance.
You ask an AI to write a function that deducts money from a user account:
# Working code (what AI gives you first pass)
def pay(user_id, amount):
user = db.get_user(user_id)
if user.balance >= amount:
user.balance -= amount
# in real life add, flush, commit
db.commit(user)
return True
return False
It runs, passes basic tests, and deducts the balance; on paper, it "works."
Why it is not correct code:
#1 Under real traffic, two simultaneous requests will double-spend because it lacks database locks or atomic updates (a classic race condition).
#2 It uses a raw float instead of integers or decimals, causing rounding drift over time.
#3 There is no idempotency key, transaction logging, or rollback if the downstream payment gateway times out halfway through.
"Working" code just survives the happy path on your machine.
Only correct code reflects the actual constraints, edge cases, and architectural reality of the system you designed.
Understood?
BTW Opus 5.5 with a good skill along with review subagents vastly reduces the cognitive load. I am still bullish on a future where humans are very high level operators at best.
Replying to @IamAroke
Please what is a correct code, because if AI gives me a working code isn't it correct?



























