Blog

Insights on engineering practice, DevOps, and using AI without losing the fundamentals — orchestrator.

Start here

The argument the rest of the collection works from.

By problem

The three problems OCOOEE is built to answer. Most readers start here.

All

Engineering Strategy & Accelerated Delivery

AI-Augmented Architecture & Delivery

Digital Transformation Services

Engineering Strategy & Accelerated Delivery

We generate code faster than we can verify it.

13 posts

AI-Augmented Architecture & Delivery

Our architecture drifts faster than we can notice.

8 posts

Digital Transformation Services

Quality depends on who is on shift.

3 posts

By topic

All

Foundation

Mindset

Method

Platform & Infrastructure

AI & Autonomy

Foundation

The engineering fundamentals that make AI-assisted work reliable.

4 posts

Mindset

How an engineer should think about AI — judgement before tooling.

4 posts

Method

The structures the work runs inside: requirements, architecture, quality.

6 posts

Platform & Infrastructure

Applied engineering: running systems, owned and sustainable.

8 posts

AI & Autonomy

The running column — where AI is going, and who decides.

2 posts

Blog

Start here

The Era of Software Abundance: Why AI Makes Engineering Fundamentals More Valuable, Not Less

By problem

Engineering Strategy & Accelerated Delivery

The Orchestrator's Edge: Why Engineering Fundamentals Are the True Power Behind AI Tools

Why Software Design Principles Are What Make AI-Assisted Work Reliable

The Language of Control: The Orchestrator's Vocabulary and Structure

The Constitution and the Dashboard: What Lives in the Repository and What Lives in the Tool

The Coder Isn't Dead — Engineering Is Worth More Than Ever

Prompts Don't Deliver Software — Engineering Does

The Orchestrator Mindset: Engineering Judgement in the Age of AI

The Instrumentation Layer: Why Orchestrators Build the Software That Sees

The Bridge Layer: Command Reference — Vocabulary, Output Contract, and Repository Standard

Requirements Are Engineering: Directing AI Without Losing the Fundamentals

Architecture Before Code: Designing Systems AI Can Build Inside

Quality Is Enforced, Not Hoped For: Automation, Gates, and Delivery

The Bridge Layer: Interface Structure for AI-Native Development

AI-Augmented Architecture & Delivery

The Door: Why Identity Is a Platform Capability, Not an Application Feature

How a Session Crosses Many Applications: The Architecture of One Login

Building It: An Order of Work for Identity and Access

Operating and Integrating It: How to Tell Which Layer Refused You

AI Parallel Development and the Verification Bottleneck

The Edge-Native Stack: What Moves Back into the Application

The Stateful Node: Architectural Vision for Sovereign Edge Infrastructure

The Second Life of Computers: A Managed Fleet — and the Edge Cloud It Enables

Digital Transformation Services

The Era of Software Abundance: Why AI Makes Engineering Fundamentals More Valuable, Not Less

The Pattern of Invention: A Historical View of Transformative Technologies

The Real AI Opportunity and Risk: Why Architecture Dictates Autonomy

By topic

Foundation

The Orchestrator's Edge: Why Engineering Fundamentals Are the True Power Behind AI Tools

Why Software Design Principles Are What Make AI-Assisted Work Reliable

The Language of Control: The Orchestrator's Vocabulary and Structure

The Constitution and the Dashboard: What Lives in the Repository and What Lives in the Tool

Mindset

The Era of Software Abundance: Why AI Makes Engineering Fundamentals More Valuable, Not Less

The Coder Isn't Dead — Engineering Is Worth More Than Ever

Prompts Don't Deliver Software — Engineering Does

The Orchestrator Mindset: Engineering Judgement in the Age of AI

Method

The Instrumentation Layer: Why Orchestrators Build the Software That Sees

The Bridge Layer: Command Reference — Vocabulary, Output Contract, and Repository Standard

Requirements Are Engineering: Directing AI Without Losing the Fundamentals

Architecture Before Code: Designing Systems AI Can Build Inside

Quality Is Enforced, Not Hoped For: Automation, Gates, and Delivery

The Bridge Layer: Interface Structure for AI-Native Development

Platform & Infrastructure

The Door: Why Identity Is a Platform Capability, Not an Application Feature

How a Session Crosses Many Applications: The Architecture of One Login

Building It: An Order of Work for Identity and Access

Operating and Integrating It: How to Tell Which Layer Refused You

AI Parallel Development and the Verification Bottleneck

The Edge-Native Stack: What Moves Back into the Application

The Stateful Node: Architectural Vision for Sovereign Edge Infrastructure

The Second Life of Computers: A Managed Fleet — and the Edge Cloud It Enables

AI & Autonomy

The Pattern of Invention: A Historical View of Transformative Technologies

The Real AI Opportunity and Risk: Why Architecture Dictates Autonomy