Topic mix
Software architecture
33 moments from 29 videos · 1:42:51 total
Clear architectural decisions prevent long-term technical debt. This collection features concise, curated highlights from senior developers discussing modular design and structured software patterns.
Play section Evolving software architecture driven by business needs
Evolving software architecture driven by business needs
Starting with basic separation of concerns allows teams to incrementally adopt complex patterns as application demands grow.
Evolving software architecture driven by business needs
Starting with basic separation of concerns allows teams to incrementally adopt complex patterns as application demands grow.
Play section Evaluating when to adopt rigorous software architecture patterns
Evaluating when to adopt rigorous software architecture patterns
While essential for long-lived systems with complex domains, strict layering is counterproductive for prototypes and simple CRUD apps.
Evaluating when to adopt rigorous software architecture patterns
While essential for long-lived systems with complex domains, strict layering is counterproductive for prototypes and simple CRUD apps.
Play section Modeling software architecture evolution with the Weasley house
Modeling software architecture evolution with the Weasley house
The ever-expanding magical house serves as a metaphor for software that must continuously adapt to new requirements.
Modeling software architecture evolution with the Weasley house
The ever-expanding magical house serves as a metaphor for software that must continuously adapt to new requirements.
Play section Defining software architecture and shared system understanding
Defining software architecture and shared system understanding
True software architecture goes beyond technical documents to establish a shared understanding of decisions that are hard to change later.
Defining software architecture and shared system understanding
True software architecture goes beyond technical documents to establish a shared understanding of decisions that are hard to change later.
Play section Recognizing technical components and proper engineering process alignment
Recognizing technical components and proper engineering process alignment
Creating an architecture that accommodates change involves organizing high-level capabilities alongside specific communication patterns defined by conways law.
Recognizing technical components and proper engineering process alignment
Creating an architecture that accommodates change involves organizing high-level capabilities alongside specific communication patterns defined by conways law.
Loading the rest of your playlist…
Your mix. Instantly.
More mixes
AI & Machine Learning
AI coding agents
AI & Machine Learning
MCP (Model Context Protocol)
AI & Machine Learning
RAG
Languages & Frameworks
TypeScript
Languages & Frameworks
React
Languages & Frameworks
Java
Cloud, Platform & Data
Platform engineering
Cloud, Platform & Data
Observability
Cloud, Platform & Data
Infrastructure as code
Architecture, Quality & Security
System architecture
Architecture, Quality & Security
Code review
Architecture, Quality & Security
Software supply chain security
Leadership, Career & Community
Engineering strategy
Leadership, Career & Community
Developer experience
Leadership, Career & Community