Software Design Retreat

There's a point in your career where more experience doesn't automatically lead to better design decisions. You can spend another year building larger projects and learning new technologies while still struggling with the same architectural questions.

AI makes this even more important. We can now generate entire features, abstractions and APIs in minutes. That's incredibly powerful, but it also means we can create complexity much faster than we can understand it.

AI can propose an architecture or generate thousands of lines of convincing code. You still need to decide whether any of it is a good idea.

The next step is developing the judgment to understand what really matters, recognize unnecessary complexity, reason about trade-offs and confidently make decisions in situations where there is no obvious right answer.

The skill lies in understanding what matters in the situation, recognizing unnecessary complexity, weighing the trade-offs, and making a decision you can explain and stand behind, even when there is no obvious right answer.

I don't want these two days to be disconnected from the software you work on every day.

You'll be able to bring your own projects, design questions and architectural problems. Maybe part of your codebase has become difficult to change. Maybe your team is debating an architectural direction. Or perhaps there's a design that works, but doesn't quite feel right.

We'll explore problems like these together, alongside carefully chosen design challenges. We'll compare approaches, question assumptions and discuss why one solution might make more sense than another.

The goal isn't to give you the "correct" architecture, but to sharpen the way you think about these decisions so you can approach the next one yourself with more confidence.

When a colleague or AI assistant proposes an architecture, you should be able to challenge its assumptions. When you're faced with an unfamiliar problem, you should be able to identify the trade-offs. And when you make a decision, you should be able to explain why it makes sense in that particular context.

I'll be there throughout the retreat as your host and facilitator. Because the group will be intentionally small, we'll have time to explore questions properly, follow interesting discussions and give meaningful attention to the problems people bring with them.

You'll also learn from the other experienced software professionals in the room. Seeing how someone else approaches the same problem can expose assumptions and possibilities you hadn't considered.

And the experience won't stop when the sessions finish. We'll have dinner together, continue the conversations, and have time to actually get to know each other.