What Is a Software Ontology?

A software ontology is a shared, explicit model of a domain. Understand what it is in Domain-Driven Design terms, why it exists, and how it works.
A layered diagram showing ubiquitous language, bounded contexts, and aggregates as the three parts of a software ontology.

How Is AI Impacting Software Engineering?

How AI is impacting software engineering: rising load on every dev ecosystem node. Software ecology explains why, and which principles to keep.
A developer ecosystem visualized as a forest with code review, testing, build, and version control nodes glowing red under AI-driven load.

What Is the AT Protocol? A Developer's Mental Model

AT Protocol explained for software developers: identity, repos, relays, AppViews, and lexicons, plus the trade-offs that matter when you build on it.
The AT Protocol showing a personal data server, relay, and AppView connected by data and query flows.

What Is the Hourglass of Uncertainty?

The cone of uncertainty narrows as projects progress. The hourglass of uncertainty says it flips again at launch. Learn which one your project is on.
An hourglass shown at three project phases: full at the start, drained at code-complete, then flipped over after shipping to production so a fresh bulb of sand begins draining through user acceptance testing.

How Do I Decode Software Deployments?

Read deployed software as a fossil record of organizational structure: service boundaries, API contracts, pipelines, and runbooks all carry team imprints.
An architect walking through a service map, on-call rotations, and runbook excerpts to reconstruct the team structure that produced them.

How Do I Diagnose Software Delivery Friction?

Use git history and the org chart to find the modules where Conway’s Law is driving merge conflicts, slow reviews, and shipping delays.
A developer running a git log query in a terminal to rank files by the number of distinct authors who edited them.

How Do I Pitch Org Design for Better Architecture?

Use Conway’s Law to connect architecture conversations to organizational design, with concrete talking points for architects, leaders, teams, and communities.
An engineer presenting a side-by-side view of a service map and an org chart to a mixed audience of engineers and product leaders.

How Do I Serve Organizational Needs With Conway's Law?

Use Conway’s Law as a diagnostic to spot healthy vs broken team-to-code alignment, then pick the organizational change that fixes the right problem.
An engineering leader comparing a commit-frequency heatmap against an org chart to identify ownership mismatches.

How Do I Smooth Platform Team Friction?

Reduce friction between a platform team and the product teams that depend on it using measurable thresholds and three communication-cost levers.
A platform engineer reviewing a queue of pull requests from multiple product teams to identify coordination bottlenecks.

How Do I Use Conway's Law?

An index of five focused guides on applying Conway’s Law: smoothing platform friction, serving the org, diagnosing delivery, decoding software deployments, and pitching a better architectural design.
A technical leader picking among five field guides on applying Conway's Law to different organizational situations.