Claude Code users are becoming the React developers of AI coding agents.
You can’t tell them there are alternatives. Yep, i said it!
So I did the comparison nobody wanted:
- Claude Code @claudeai vs
- Codex @OpenAIDevs vs
- OpenCode @opencode
Remember, I'm just the messenger, don't shoot me 😂
https://t.co/2koI69t1dU
I have not been this excited about technology in over 20 years. As an IC turned Manager/CEO I have gone with several years with no commits, to several commits daily. Rght now, I am building, deploying & operating full stack without leaving claude and it feels like the future.
We've seen this one play out a few times now.
The team is under pressure to ship, and the deadline was yesterday. The DevOps engineer, with three days of bad sleep and back-to-back standups, is moving fast through YAML configs just to get it over the line.
Two weeks later, there's an incident. The database was publicly exposed. The customer’s data was accessible.
Not because anyone was careless. Not because they didn't know what a secure config looks like. They knew. They were just moving too fast, in a moment where one missed setting was all it took.
Around 80% of cloud security exposures trace back to misconfiguration. Not sophisticated attacks. Not zero-days. Just configuration drift, skipped steps, and good engineers in bad conditions.
The pattern is always the same: the pressure comes from the business, lands on the delivery team, and the thing that gives first is the thing nobody can see until it's too late.
Shipping slower isn't the answer. But building a process that only holds together when your team is well-rested and unrushed — that's the actual problem.
The teams that stop having these incidents aren't more careful. They've just removed the steps that depend on someone remembering.
The teams that stop having these incidents aren't more careful. They've just automated the parts of the process where human error under pressure is almost guaranteed.
Standup meeting this morning "I was watching the agent in Prod last night and I see its hallucinating that its 2025..." - sentences I would never have guessed I would be hearing regularily.
My co-founders Jaco Nel, Deen Hans and I have spent the last 15 years helping developers operate production software. As software engineers, as team leads, as architects, as engineering managers, as CTOs.
During this time, it became clear to us that developers generally know what the right thing to do is - it's just that so much is stacked against us, that best practices are the first thing to go when pressure mounts.
Every (serious) developer knows why tests matter. We know why security is important. We know why instrumentation and observability are key to operating software in production. So why do these operational domains get ignored so often?
Each developer, team and organisation is different, yet patterns emerge.
- Ambitious boards and founders. Leadership always chooses time-to-market (speed) & growing market share.
- Feature Factories: Companies tend to prioritise features over anything else.
- Scarcity: Experienced DevSecOps engineers are scarce. Industry standards show 1 Security engineer supporting 70-90 developers and about 10 SWEs for every DevOps engineer.
- Infrastructure complexity and tooling fatigue.
We know what the right thing to do is. We simply don't get the time, resourcing or focus to do it properly. We prioritise speed. We accept more tech debt in favour of features. We ignore best practices as we don't have the time to deal with infrastructure and tooling complexity.
We don't think we can change this. But we can change how hard it is to do the right thing.
So we built https://t.co/PS33ueED5v.
- Modern developer workflows, from commit to production
- Enterprise infrastructure built for purpose
- AI that operates, so you don't have to do it all
Connect your code. We handle infrastructure, deployment, scaling, security, and operations. Automatically.
The platform is live and already making a difference for our customers.
Follow along for the journey. A story about software engineers that have had enough, a story about turning the tables on everything that stacks against us.
@Salus_Cloud
I despise wasting time. I try time it that i'm the last person on the plane. If your name has not been called over loud speaker in an airport for final boarding, are you even living?
Who is the best AI/Agentic Software Engineer that you know? Id like to attempt to hire them. Happy to pay $1000 referral bonus to anyone for a successful placement. Salary range anywhere from $5000 - $8000 per month plus equity. https://t.co/TRZJlvRsbW
Remote OK. CT base pref.
1x YC rejection
3x VISA rejection
More than 20x VC rejections
Over 100 cold pitches ignored
7 months FDD & LDD
4x investor Yeses
No foreign degrees, blue passports or prestige alumni communities.
Not bad for a couple dudes from Isale-Eko and Ilorin.
@Salus_Cloud Many thanks to our team, our early adopters and our investors who are all playing significant parts on a mission that matters.
https://t.co/PvkOsNOW1U
https://t.co/3mEk3giyug
Best practise, AI-Native, enterprise grade software delivery & operation doesn't belong to big Budget IT departments. It should be accessible to all. This $3.7M funding injection is going to help us level the playing field.
@Salus_Cloud May Salus Cloud ( https://t.co/JxgmcRtZPY ) succeed in its mission to protect & secure technology operations for many companies across Africa and beyond.
Please join us on our mission.
migrated @Salus_Cloud to @GetPaidHR in less than 1 month. Ran Payroll for the team seamlessly yesterday. Im a CEO sitting in Cape Town, using @GetPaidHR to manage, retain, hire and pay a global staff complement and I am happy customer. I recommend them. Thanks @seyedele
6 months to close a SEED round of $3M+. Closing it right now. I learnt so much. Made so many mistakes. Cant imagine how hard it must be for first time founders from Africa. Will share more as it closes officially.
The Developer Platform of the future is coming soon @Salus_Cloud