Building simple iOS apps with #codex is the greatest experience of all time. I wouldn't even call it work. When I build and own something there's an inner fire that's indescribable.
#codex and iOS development is 🔥
XcodebuildMCP + an iPhone simulator + allowing the screen recording setting makes #codex unstoppable.
The model doesn't make mistakes.
It makes me curious to push the complexity.
@morganlinton Codex asks for my approval for every file change and I can't quite figure out how to auto approve them. I've implemented -yolo mode, approved nearly all non-destructive commands in an allow list, and have approval_policy = "never" in my global config.toml. Any ideas?
The principle:
AI isn’t replacing human intelligence — it’s reflecting it.
When your system is clear, focused, and creative, the code feels alive.
When it’s vague, everything feels “off.”
That’s not the AI’s fault.
That’s the mirror talking.
Sometimes AI builds exactly what I asked for — and it still feels wrong.
No syntax errors. No crashes.
Just… wrong.
Took me a while to realize:
That feeling isn’t about AI.
It’s about me. 👇
AI’s creativity is only limited by yours.
Its precision only as sharp as your systems.
Its brilliance only as wide as your curiosity.
You set the ceiling.
“My crypto got hacked — and I had 2FA on.”
You’ve probably seen that post. Maybe even lived it.
The worst part? It’s not just personal failure — it’s systemic neglect.
In systems thinking, every failure ignored becomes an amplified feedback loop.
Crypto can’t grow if users don’t feel safe.
In Buddhist terms: awareness without accountability is delusion.
It’s time exchanges wake up — or risk watching trust disappear faster than their tokens.
For Builders & Exchanges:
Security isn’t a feature — it’s a public good.
If you profit from custody, you inherit responsibility.
Fix fake-site detection. Enforce phishing takedowns. Educate in-app, not in fine print.
You don’t get to say “not our fault” anymore.