Software development, architecture and team organization and leadership
Software architecture, development and team organization and leadership¶
This site has two interwoven parts. The first is a reference glossary for software architecture, development, and team leadership: precise definitions, cross-linked terms, and methods for practitioners. The second is a personal Garden Atelier: notes on what I am learning, experiments I am running, and ideas I am crafting toward better software and better leadership.
The glossary shows what things are. The atelier shows what I am making of them.
Both grow over time and feed each other. Because the human nature and software development influence each other (see Conway's Law), the boundary between reference and reflection is intentionally blurred.
Foundations¶
Software Architecture · Technical Debt
Architecture & Strategy¶
Domain-Driven Design · Residuality Theory · Wardley Mapping
Team & Organization¶
Architecture for Flow · Conway's Law · Inverse Conway Maneuver · Team Topologies
Methods¶
Architecture for Flow Workflow
Perspectives¶
Perspectives on Residuality Theory
Garden Atelier¶
Architecture & Strategy/Documentation¶
Arc42 · Architectural Decision Record
Architecture & Strategy/Domain-Driven Design¶
Architecture & Strategy/Residuality Theory¶
Antifragility · Stressor Event
Architecture & Strategy/Wardley Mapping¶
Climate · Doctrine · Persona · Situational Awareness · Value Chain
Foundations/Software Architecture¶
Quality Attributes · Software Analytics
Team & Organization/Team Topologies¶
Cognitive Load · Enabling Team · Platform Team · Stream-Aligned Team · Team API
No interactions found yet. Be the first! Link to this page on your blog, send a Mastodon toot, or leave an annotation via Hypothesis with the button "annotate" at the navbar to appear here.