Software architecture
34 moments from 31 videos · 1:46:54 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.
Understanding the role of software architecture and quality
How architecture and design address non-functional requirements to build high-quality scalable systems.
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.
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.
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.
Architecture fundamentally defined as a set of decisions
Defining software architecture logically as a continuous stream of context-dependent choices.
Navigating real world software architecture collaboration
Bad software is often a communication problem that requires defining actual business needs before implementation.
Preventing software architecture deterioration over product lifespans
Maintaining dedicated architectural oversight prevents escalating maintenance costs and continuous integration delays.
The primary purpose of software architecture decisions
How good architectural practices fundamentally serve to save time and accelerate market delivery.
Applying effectiveness concepts throughout the software architecture lifecycle
Incorporating non-functional requirements during business and enterprise architecture planning ensures long-term structural efficiency.
Building engineering cultures that support long-term software architecture
How prioritizing alignment among management, technical leads, and business missions dictates the invisible systems that ensure product success.
Designing poor software architectures by ignoring Conway's law
Grouping developers by technical profession instead of value streams creates monolithic bottlenecks that mirror poor organizational structures.
Software architecture overview using the C4 model
Using the C4 model to map out a microservices architecture communicating with a central data hub.
Redefining developer roles and software architecture requirements
Since AI agents can now handle basic coding tasks, early-career engineers must pivot toward mastering software architecture and complex spec writing.
Optimizing software architectures to minimize infrastructure resource drain
Architectural decisions around processing approaches, storage volumes, and unused dark data heavily dictate both ecological outcomes and cloud service costs.
Building architectures for evolving business capabilities
Software platforms must be constructed to support continuously changing feature sets as business operations expand and demand new services.
Balancing architectural trade-offs without silver bullets
Why software architecture requires balancing practical trade-offs rather than searching for perfect solutions.
Improving software architecture skills through consistent writing habits
Detailing software functionality deepens fundamental architectural understanding, strictly supports legal compliance, and inherently leads to cleaner implementations.
Applying YAGNI and KISS to architectural decisions
Applying foundational software architecture principles minimizes unnecessary dependencies and prevents over-engineering simple solutions.
Introduction to software architecture documentation challenges
Common issues include missing, scattered, or overwhelmingly large architecture documentation formats.
Applying typology to categorize software architecture patterns and concepts
Grouping scattered source files into technical and business classifications establishes a higher-level abstraction for comprehending system frameworks.
Defining design decisions across code, solution, and application levels
The different tiers of technical choices and where architecture decision records appropriately apply.
Core responsibilities of a software architect in development
Defining requirements, designing solutions, and continuously validating implementations ensures software meets overarching business goals.
Understanding the unique characteristics of software complexity
The invisible and highly changeable nature of software requires intentional architectural translation.
Reducing accidental complications in software architecture
Strategic refactoring strips away unnecessary technical baggage caused by disjointed development styles and brute force problem-solving.
Aligning system structure with domain-driven design
Software architecture structures should fundamentally reflect domain logic rather than relying exclusively on generic technical patterns.
Three reasons why software architecture must be iterative
Domain models mature, functional requirements pivot, and developer skills improve over time, demanding an iterative architectural approach.
Applying cognitive schemas to software design patterns
Organizing logic with consistent architectural patterns leverages human cognitive schemas for faster code comprehension.
Four dimensions driving modern software architecture complexity
Distributed architectures, containerization, orchestration, and demanding uptime requirements necessitate advanced tooling.
Writing readable code architectures to clarify infrastructure intentions
Moving beyond immense text-file declarations immediately enables development teams to effectively assess architectural integrity while simultaneously recognizing established functional logic.
Aligning software architecture with non-functional requirements
Using the ISO 25010 standard to prioritize foundational attributes like reliability over unconditionally applying trending microservices.
Balancing modularization fundamentals with effective software engineering organization design
Successful service architecture heavily depends on aligning technical module boundaries with fundamental team structures.
Establishing an integrated developer platform for scaled engineering
Adopting an opinionated reference architecture helps scale agile methodologies across large software engineering organizations.
Introduction to Wardley Maps in software architecture
Wardley Maps provide a visual framework for planning strategic evolution and modernizing older software systems.
Building and maintaining sustainable software architectures
Maintaining a steady stream of feature delivery over multiple releases requires continuous attention to structural health and refactoring.
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