Joined January 2020
Osinachi Okpara retweeted
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.
55
14
6
601
30,234
Osinachi Okpara retweeted
They’re cooking in the new avatar👀👀
1
1
6
190
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.'
29
30
10
478
25,589
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? 🙃
today was my last day in cloudflare (again). the best career and opportunity in my whole life, and the closest friends I would die for. thank you to everyone who made it all so special. I had an incredible time. 🧡
3
29
2,919
Osinachi Okpara retweeted
Meet Kimi K3.1 Pro, our most capable 3T-class model.
257
675
300
8,724
320,776
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?
1
3
83
Osinachi Okpara retweeted
Introducing Kimi K3.1 Pro: our most capable 3T-class open-weight model. 🔹 1M-token context, 2.8T total / 104B active params (MoE), Multimodal. 🔹 Full-project coding: games in Unreal, Unity & Godot. 🔹 Excels at parametric 3D modeling in Blender & CAD. 🔹 More reliable at finance work: Accurate modeling with hallucination down by 65%. 🔹 Matching the strongest proprietary models across coding, agentic and knowledge benchmarks. Kimi K3.1 Pro and K3.1 Pro Highspeed (2–3× faster) are now live on Kimi.ai, Kimi Work, Kimi Code, and the Kimi API. Open weights by Nov 4, 2026. 🔗 API: platform.kimi.ai 🔗 Tech blog: kimi.ai/blog/kimi-k3-1-pro
921
2,407
1,828
22,134
1,845,978
This seems bad.
111
1,925
138
39,929
770,758
Osinachi Okpara retweeted
Kimi K3.1 Pro benchmarks are here, it is the best open-weight model in the world.
11
19
3
220
15,832
Osinachi Okpara retweeted
Just a few years ago, management could comfortably wait out a two-week sprint to get a feature shipped. Today, there’s growing impatience when a feature takes more than 24 hours to deliver. 🥲 The pressure on software engineers right now is crazy, and I don’t think we’re talking about it enough. I can barely get two sentences into explaining my implementation plan before someone interrupts with: “Just give it to Claude to do!” “Sir, we need to think about…” “That’s what Claude is there for. Let it do the heavy lifting!” A task gets assigned, and barely 10 minutes later: “Why is it taking so long? Aren’t you using Claude properly? This should take a minute or two!” Somehow, the existence of AI has created this assumption that software engineering is now just a matter of writing a prompt and watching features magically appear. Nobody wants to hear about architecture, edge cases, testing, security, or the implications of a poorly thought-out implementation. Just ship it. And ship it NOW. AI has become both a blessing and a curse. Something I genuinely expected to reduce my workload has instead increased it. The productivity gains are real, but so are the expectations that come with them. We’ve made development faster, but somehow, we’ve also made every delivery feel slower. And that’s the irony nobody seems to be talking about. Omo mehn, I’m just exhausted, might as well just resign, but it seems it’s the same everywhere😪
I want to talk about something that’s really been stressing me out and draining me mentally.
45
109
32
372
17,396
Osinachi Okpara retweeted
"Personalisation of the UX will let the user feel closer to the product" The user:
161
523
417
2,120
214,860
Osinachi Okpara retweeted
i'm begging you: stop applying on job boards. cold email founders instead. the exact play, with the data: 1. find 25 startups that raised a seed round 2 to 9 months ago. fresh money means hiring. under 2 months they're still scrambling. free sources: inc42 and entrackr funding trackers, wellfound's recently funded filter. 2. keep only the ones under 30 people. below 30, the founder still reads their own inbox. 3. pull 2 contacts per startup: the founder plus whoever runs the function you want. emailing more than one contact lifts replies 93%. 4. the email: 90 to 120 words. line 1 is about their raise or their product, not you. subject 36 to 50 characters (long subjects get 32.7% more replies). personalize the body (+32.7%). no resume attached. end with one question: 'what are you struggling to hire for right now?' 5. send wednesday morning, 9 to 11, their timezone. best day in the data. 6. follow up once on day 4. a single follow-up adds 65.8% more replies. once more on day 9, then stop forever. 7. the math: 25 startups x 2 contacts = 50 emails. average cold outreach converts 8.5%, that's 4 replies even done plainly. stack the multipliers and you're at 8 to 12 replies, 3 to 4 calls, 1 to 2 offers. 50 emails and one weekend to build the list. job boards put you in a queue. this puts you in a conversation.
44
114
22
2,314
156,211
Osinachi Okpara retweeted
A good day to remind you all that failure is a part of the journey: ayomideoyekanmi.medium.com/o….
Back in 2021 I interviewed at Vercel and I failed badly. I couldn’t implement a debounce function and was stuck for like 30 minutes. It was pretty embarrassing. 10 months later (2022) I interviewed again and got the job. Don’t give up!
5
33
5
162
10,369
I've noticed poteto I'd incredibly interested in bendlang. I've seen so many posts/comments from her about it I'm genuinely looking forward to stuff she's building with/on it.
Replying to @aidenybai
yup, very hard problem but hopefully we will see more innovation in formal verification (+ keeping code/spec in sync, ideally in same lang like @bendlang)
1
2
331
What is autocorrect doing to me? 😭
26
It's been long since I resonated with an experience like this. I'm nice/kind because I understand what it feels to be on the other end of "not-nice/kind" people. It's also why I go out of my way to help people. "we present the opposite of our fears."
2
6
304
Osinachi Okpara retweeted
Replying to @emilkowalski
5 years ago: can you write a debounce function today: do you understand 'debounce' as a concept The vocabulary and ability to navigate the conceptual space has become more important than the code. Case in point 😁 github.com/emilkowalski/skil…
19
18
8
639
38,528
Osinachi Okpara retweeted
I bombed two interviews the past year so bad that they might mortify me until the day I die appreciate the homies talking about this this week; it's so easy to celebrate wins & paint a picture of being a perfect angel but this life can humble all of us
I interviewed at Figma in 2024, and bombed a middle interview so so so badly. I never got another shot lol. Sometimes you bomb: but I learned a massive amount and rebuilt everything from it. Got a role not to long after.
4
3
4
138
11,989
Osinachi Okpara retweeted
Someone from the chat asked for advice, they are graduating with cybersecurity degree.... Here's what I told him
13
6
1
242
11,507