Someone needs to spot when a linked list is better than a map. And the other needs to spot when clinical trial coding should happen before claims, audits, or patient outreach.

It’s a new frontier, and there are no absolutes. But I suspect the most durable AI systems will be built around highly composable, well-orchestrated agents.

Customer: “I don’t want to pay more than $100/mo for my website” Developer: “What are your goals?” Customer: “1M daily visits, 1,000 monthly signups.”

And we've spent the past 25 years offering serverless compute, auto-scaling, pay-as-you-go for AWS and Internet infrastructure. And the economics are still a hard sell.

The GPT models are highly steerable. So I suspect the "soul" is working as expected.

(for context, in OAI enterprise background agents, they have no personality. They just get 'er done)

Edge AI on iPhone, however... many potential applications around vision, hearing, interpreting your surroundings in real-time.

See Bezos' playbook for Amazon. They weren't profitable for years.

We're only using 1% of what these models will ultimately do when they're running 24/7 as utilities serving new economic models.

There just isn't enough compute right now to realize the larger monetization strategies.

Many teams remain anchored on equating AI with chat experiences, while a growing share of enterprise value is emerging from leasing compute clusters to run agentic workloads in containerized environments.

OpenAI has built a cloud-first architecture that supports this model. The desktop experience and applications are sexy, but enterprise usage will likely skew heavily toward asynchronous, background processing.

Distilled mini/nano models need regular reminders about their objectives.

As documented by Manus https://manus.im/blog/Context-Engineering-for-AI-Agents-Less...

The markup includes self-describing metadata and constantly reminds the GPT model of explicit context.

If coding agents already read AGENTS.md before making changes, they can also maintain a TECHNICAL_DEBT.md checklist.

Keep the loop intact: AGENTS.md ensures technical debt remains in context whenever changes are planned.

If I can run resume {session_id} within 30 days of a file’s latest change, there’s a strong chance I’ll continue evolving that story thread—or at least I’ve removed the friction if I choose to.

Whereas OpenAI won their contract on the ability to operationally enforce the red lines with their cloud-only deployment model.

That's not the case. OpenAI is advancing on many fronts; codex, vectorStore, embeddings, response API, containers, batch processing, voice-to-speech, image generation... the list goes on.

Eventually the culture will come around to: a) build new sh-- quickly with AI b) build a new productivity stack

A commercial RAG solution would use Query Expansion (QE) and examples to find nearest neighbors.

I still believe there's a mise en place step before doing the thing, when quality counts.

But it was only a matter of time before: a) Microsoft reclaimed its IDE b) Frontier model providers reclaimed their models

Sage advice: don’t fill potholes in another company’s roadmap.