Ogbonna Sunday

I spent $500 on Google Ads for my agency. 7,500 impressions. 400 clicks. 0 calls booked. The clients we actually closed? All referrals. Lessons: → Ads don't replace trust → Founders don't buy code, they buy certainty → If they don't know you can deliver, no landing page saves you Stop running ads before you've built an audience. Build trust first. The calls will come 👌

6 + 6 =12 * 6 = 72

Introducing Apex: a specialized, cost-efficient coding model for React Native. Built by Callstack for the work our engineers do every day: building apps, fixing framework-specific issues, reviewing architecture, and shipping one codebase across platforms. Now opening in private beta.

You might believe you should spend less time thinking about code because of AI. I strongly disagree! We’re watching this play out live where tons of AI generated code becomes a liability. At the end of the day, an engineer needs to be responsible / on call for code that gets shipped to production. If you don’t understand the system you’re trying to debug, you’re probably going to have a bad time. Yes, AI can help with all of this, if you set up the proper systems. You can have agents triage prod logs, look at errors, etc. You can speed up parts of the investigation, but an engineer needs to make the call. There might be serious customer or financial implications from that change. I expect the trend continue for trimming dependencies, vendoring code so you can modify it directly, preferring simpler systems with fewer abstractions, and spending waaaay more time thinking about system design and code maintenance. I’ve said this before, but it’s a great time to get familiar with CS fundamentals and some of the history behind what great software looks like. Many parts will be different in the coming years as AI progresses, but also a lot more than people realize will stay the same.

How to actually get the most out of Codex instead of bookmarking another great guide you’ll never open again: We turned this article into an interactive workbench. Before prompting Codex, open the workbench, choose your task type, and check whether you’re using the right Codex capabilities. Built by Codex inside Open Design. If you want the workbench, reply “Open Design” below and I’ll send it to you.

Introducing Composer 2.5, our most powerful model yet. It's more intelligent, better at sustained work on long-running tasks, and more reliable at following complex instructions. For the next week, we’re doubling the included usage of the model.

Your package list is part of your product risk. Before launch, know which dependencies touch auth, payments, and user data. We catch exposed packages in almost every pre-launch audit we run. Which ones does your team actually understand?

Introducing Zero The programming language for agents. I wanted a systems language that was faster, smaller, and easier for agents to use and repair. Explicit capabilities. JSON diagnostics. Typed safe fixes. Made for agents on day zero.

You don't need a CTO yet. You need someone who can challenge estimates, question the architecture, and stop bad decisions before they cost you. Are you hiring a title or solving a real problem?

Payments failed. Users tripled. Data leaked. AI built the screen. It had nothing for what came next. Founders call me when that hits. The model stops. You don't get to. Where are you still assuming AI has an answer?

At Amazon, workers faked AI tasks to hit quotas. That's what "use AI more" as a goal produces. Faster delivery. Fewer mistakes. Cleaner products. Those are the goals. Is your team chasing activity or outcomes?

A bad hire starts before the first call. 7 things to write before you speak to a developer: 1. The problem 2. Who has it 3. What success looks like 4. What you won't build 5. Your timeline 6. Your budget 7. How you'll know it's done Which one costs the most to skip?

AI built your MVP in a weekend. Now who decides your architecture? Who owns your security model? Who tells you what to build next? None of that lives in a prompt. That gap is where startups lose money. Which of those decisions are you still sitting on?

Most founders hire developers too early. Skip validation: you build what nobody wants. Skip scope: your budget doubles. Skip the senior review: you won't know it's broken until launch. Skip one and you're paying for guesswork. Which do you skip most?

@svpino 🤣🤣🤣

The “buy a Mac mini or you’ll never make it” crew moved on already. The whole “I’m making $10,000/mo with OpenClaw in a Mac Mini” was a grift, and it’s now dead. What’s the latest now? DGX Spark?

If you use ai for non-coding works, then stick to Claude. Codex is king when it comes to coding… but Claude still has some edge on other things

Now Remodex is kicked out 🥲🥲

You've been asking for this one... Now in preview: Codex in the ChatGPT mobile app. Start new work, review outputs, steer execution, and approve next steps, all from the ChatGPT mobile app. Codex will keep running on your laptop, Mac mini, or devbox.

Your tech stack follows you. Into hiring. Into security. Into your rewrite timeline. Founders call it a developer choice. It's a business risk. Who owns it in your company?

This is awesome

More AI agents, more management tax. Your dev ships 3x more code. You review 3x more code. The AI does the typing. You still own every decision. How's your overhead holding up?