NO SILVER BULLET

Episode notes: https://threedots.tech/episode/overcomplicated-vs-oversimplified-code/Quick takeawaysComplexity comes from two extremes - projects fail both when they’re overcomplicated with unnecessary patterns and when they’re oversimplified for a complex domainEssential vs accidental complexity - essential complexity comes from the domain itself and can’t be removed, accidental complexity is created by poor implementation choices“Keep it simple” is lazy advice - achieving simplicity takes effort; closing your eyes to complexity just pushes it elsewhereMatch patterns to the problem - using the same approach everywhere is a red flag; mix simple solutions for simple parts and sophisticated patterns for complex domainsShip fast and iterate - if you can’t deploy daily and fear making changes, something is wrong regardless of whether it’s over or under-engineeredWe discuss where complexity in software projects comes from and how to deal with it. There are two common extremes: projects that are overcomplicated because someone applied patterns they saw at a conference without understanding them deeply, and projects that started simple but became a tangled mess as they grew.Both can be equally difficult to work with. The key insight is understanding the difference between essential complexity (inherent to your domain) and accidental complexity (created by your implementation choices). We share diagnostic signals to identify unhealthy projects and practical advice on matching your tools to the actual problem you’re solving.No Silver Bullet paper by Fred Brooks - discusses essential vs accidental complexityDomain-Driven Design (DDD) - a pattern for tackling complex domainsClean Architecture - another approach for managing complexityYAGNI (You Aren’t Gonna Need It) - principle against premature generalizationDefensive programming - validating inputs early to prevent errors propagatingCanary releases and rollbacks - deployment strategies that can add overheadThree Dots Labs blog - articles on Go patterns and architectureGo with the Domain ebook - free ebook about DDD in Go with 60,000+ downloadsWild Workouts example DDD project - complex Go project demonstrating real-world patternsMicroservices architecture - discussed as sometimes adding unnecessary complexityCRUD applications - simple approach that works for some domains but not othersThe Domain Engineer training - upcoming training mentioned for early next year

Full episode notes: ⁠https://threedots.tech/episode/ddd-toolbox-not-religion/Quick takeawaysDomain complexity matters more than technical complexity - Most projects fail not because of technical challenges, but because they don’t handle the business domain well.DDD is a toolbox, not a religion - You don’t need to use every pattern from Domain-Driven Design. Pick what solves your actual problems.Start with the domain model - Understanding how the business works is more important than designing the perfect schema.Avoid solving imaginary problems - Spending months on frameworks or platforms before building actual features often leads to wasted effort.Strategic patterns are essential for everyone - Even if you don’t use tactical DDD patterns, thinking about core domains and module boundaries matters in every project.In this episode, we discuss why software projects become legacy code that nobody wants to touch.We talk about how Domain-Driven Design can help, but also why it’s often misunderstood or overused.Instead of treating DDD as an all-or-nothing approach, we suggest to use the ideas pragmatically - picking the patterns that solve real problems in your project.We share stories to show how focusing on domain complexity rather than technical complexity leads to better software.

In this episode, we talk about why software projects in regular jobs are delivered much slower compared to side projects, and what you can do about it.We share our journey from building hobby projects as teenagers to working in professional environments, and the differences we encountered.Developers are often kept isolated from product decisions and treated as “coding monkeys in golden cages” - just receiving tasks without understanding the why behind them.We discuss techniques like Event Storming that can help break down these barriers, and improve collaboration between developers and product managers.

After the summer break, we're back with a new season of No Silver Bullet. New episodes every second Wednesday.

Episode notes: https://threedots.tech/episode/ama-1/Quick takeawaysGo in the AI era: Go is excellent for AI applications, as the built-in concurrency makes orchestrating parallel API calls much easier than languages like PythonArchitecture philosophy: Clean Architecture isn’t always necessary. Start simple and add layers only when you feel the pain of complexity, not because someone said you shouldCareer transitions: Switching roles within tech is easier internally. Moving from sysadmin to developer works better within the same company where people already trust youGo design patterns: Small interfaces near usage is the Go way. Duck typing allows you to define interfaces where they’re used rather than in separate layersDistributed systems: Async communication often solves sync timeout issues. When dealing with chains of service calls, consider using messages instead of increasing timeoutsIn this special 10th episode, we answer community questions in our first AMA format before taking a summer break.We discuss Go’s role in AI development, Clean Architecture implementation, career transitions in tech, and distributed system timeouts.After the break, we’ll switch to pre-recorded episodes with improved production quality. We still plan running some live episodes like this one, so stay tuned!