Daniel Aranda

Big Data • Cloud Technologies • Serverless • Product Builder • Systems Architecture • Financial Vertical • High-Leverage Engineering • Decision Systems

[Daniel Aranda @javierdaniel]

React is a state-based framework, but a lot of people use it like jQuery with JSX.

Then AI learned from that code.

Now Codex, Claude, etc. happily generate useEffect abuse, duplicated state, ref hacks, and DOM patching.

React is not the problem.

The mental model is.

[Daniel Aranda @javierdaniel]

@Xxi5olc @awilkinson Might be worth checking the setup/workflow. I’m using 5.5 in Codex and it’s been noticeably faster for me than Claude Code on comparable tasks.

What kind of task/repo is taking 25 minutes?

[Aashish Ranjan Singh @_aashish_singh_]

Told a dev to switch from Cursor to Codex with GPT-5.5.

He showed me his screen: "I'm already on GPT-5.5 in Cursor. Same thing, right?"

Bro. That's not the same thing.

The model is the engine. The harness is the entire car.

Tool routing, context strategy, agent loops, system prompts — Cursor and Codex differ on every single one. Same GPT-5.5 in different harnesses produces wildly different outcomes. Different cost. Different reliability. Different ceiling.

The model is maybe 30% of the actual experience. The harness is the other 70%.

How do you explain this to people without sounding like a snob? 😂

[Daniel Aranda @javierdaniel]

@thsottiaux I hope someone rethinks the limits.

In this AI era, a weekly reset feels ancient. A 5-hour to 3-day reset window would be far more reasonable.

[Daniel Aranda @javierdaniel]

@matt_gray_ This says less about AI’s leverage and more about how you view people.

I’m an AI advocate and use it daily; it helped me go from architecting and coding everything myself to architecting systems and delegating better.

But treating human needs as defects is the sick part.

[Daniel Aranda @javierdaniel]

@cryptogems555 @grok @BitcoinPulseX

[Daniel Aranda @javierdaniel]

@Luke_Unedited4U @cyrilXBT OpenAI began as research-first, not profit-first.

Products changed that, same as the rest of AI.

@elonmusk is just being combative here.

[Daniel Aranda @javierdaniel]

@everyonebpup Why is everyone suddenly writing in greentext / 4chan format here? Been seeing it everywhere lately. Write normal please.

[Daniel Aranda @javierdaniel]

@DragonStacker @bridgemindai I agree. And even the frontend/design part is becoming less of a gap.

Create a strong mockup with GPT Image 2, then have it implement it. The results can be genuinely professional-grade.

[Daniel Aranda @javierdaniel]

@jasperdevs @TechnikBlogEu @sama Post your prompt and outputs from both, many of us think you are the problem but if show real examples that will probe your point.

[Daniel Aranda @javierdaniel]

Anthropic acting like they’re playing 4D chess while repeatedly shooting themselves in the foot.

Claude had the love of developers. They had momentum. They had trust.

Then came worse product decisions, unnecessary limits, and self-inflicted damage.

[Daniel Aranda @javierdaniel]

Hey @thsottiaux

Would love your thoughts on this, shared some UX feedback for the Codex experience for power users.

I think there’s a big opportunity in reducing cognitive load and making context/state much more visible.

https://t.co/HUmFVUhXJR

[Vivo @vivoplt]

The hiring process in tech is completely broken.

- Round 1: Recruiter screens you for 15 minutes.
- Round 2: Technical phone screen.
- Round 3: Take-home project. "Should only take 4-6 hours." Takes 20.
- Round 4: On-site. 5 back-to-back interviews.
- Round 5: "Culture fit" chat with the founder.
- Round 6: Reference checks.
- Round 7: Waiting. Silence. Ghosted.

Meanwhile the guy who got hired knew someone on the team.

6 rounds of interviews defeated by one LinkedIn connection.

[Daniel Aranda @javierdaniel]

@fahmitech @vivoplt The ideal process? Let the people who feel the outcome decide.

Too often, engineers are evaluated only by other engineers protecting their comfort zone.

Some of the best builders get filtered out not because they lack skill, but because they think faster.

[Daniel Aranda @javierdaniel]

@CaptainInsightX @0xPrajwal_ Did not you say they delivered the SAME thing?

[Sam Altman @sama]

Codex can learn from experience and proactively suggest things it can do for you.

It now has an in-app browser, many new plugins, and so much more.

[Daniel Aranda @javierdaniel]

Stop reading logs. Start reading signals. ⚡

A powerful dashboard to understand your AI spend, session burn rate, and budget risk in real time.

Built on top of @agentbudgetsdk

https://t.co/9mL0wDsuWr

@twtofsahil

[Daniel Aranda @javierdaniel]

🚀 AI is no longer just a coding assistant — it’s a force multiplier.

From coding → orchestrating.
From 1 horsepower → 20 horsepower.

The engineer’s role is evolving toward architecture, product judgment, and execution orchestration.

[Daniel Aranda @javierdaniel]

Built a real-time observability dashboard for @agentbudgetsdk 👀

Hard budget limits are only half the story.

Teams also need to see:
• where spend moved
• what caused the spike
• whether burn is accelerating
• when exhaustion becomes likely

[Daniel Aranda @javierdaniel]

@nbrempel Would love to hear more about what you built with Opus that you haven’t been able to achieve with Codex.

For context, I’ve built many frontend UIs with Codex and the results have been genuinely great, especially when the prompting is design-specific and iterative.