The core conflict in software development is balancing the aspirational desire for a perfect system with what is practically sufficient to ship.
Choosing between a design system and custom code involves trade-offs with accessibility compliance, brand identity, and team maturity.
A practical example shows how to structure a React and Gatsby application to cleanly separate data logic from UI components using DTOs and context.
As a project grows, evolving to a multi-repository micro-frontend architecture requires shared component libraries, project templates, and centralized services.
Overly complex patterns like hexagonal architecture can become a bottleneck for teams with mixed experience, necessitating a pragmatic simplification.
Pragmatic architecture choices must be fluid and conscious, balancing project size, potential for evolution, and the team's collective skill set.
Jobs that call for the skills explored in this talk.