How Do I Use a Software Ontology?
Put an established software ontology to work in daily workflows, design sessions, and database schemas; keep it fresh and make it usable by the whole team.
How Do I Create a Software Ontology?
Create a software ontology with Domain-Driven Design: capture the ubiquitous language, draw bounded contexts, and model aggregates into a shared map.
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.
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.
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.
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.
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.
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.
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.
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.
