Hi there,

I’ve seen architecture decisions that were perfectly defensible when they were made, then became difficult to live with as the system and the teams changed. The difficult part is seeing enough of those consequences before you commit, and explaining the trade-offs clearly enough that others can make good decisions around yours.

That’s the work I want to do with you in the InfoQ Certified Architect Program. For four hours each week over five weeks, you’ll look at decisions from your own work alongside senior engineers and architects from other companies. You’ll examine the alternatives, the constraints that matter in your organization, and the effects on the teams who have to live with the result. I’ll share what I’ve learned working on architecture across different systems, and your peers will bring perspectives you may not have inside your company.

You should be able to take that thinking straight back to work, whether you need to make a call, revisit one that isn’t working, or explain to your CTO why you’re recommending one option over another. Chinmay Sawaji, who joined an earlier cohort, told us he now articulates trade-offs more clearly in proposals at work. That is a much more useful outcome to me than simply leaving with another set of patterns to remember.

I’m facilitating the next cohort, starting October 9. It’s live online and costs $1,470.

Take a look at the dates and join the cohort

If you’d like to know whether the decisions you’re working on fit the program, you can reply to me here.

Best,