Hope you had a cool month! We’ve been enjoying every last minute before AI takes over every aspect of our jobs. If all else fails, IcePanel will pivot to making panels of ice 🧊 .

We’re kicking off this issue with a post from Ilya on the transition from developer to architect. Growing into an architect is about moving beyond code and pure technical problems to thinking about tradeoffs and outcomes.

Episode 3 of Dear Architects, with the super-intelligent (human) Susanne Kaiser, covers a range of topics from Wardley Mapping, Event Storming, and Team Topologies. Software design and architectural thinking don’t slow teams down, they set guardrails on AI that, left unchecked, will amplify existing problems at scale.

This month, our team had a long chat to discuss the future of architecture and what it means for IcePanel. I doubt we’re alone (see how SaaS has performed in the public markets this year) in facing tough questions on what it means to exist in this new world. We had some fantastic discussions, and we’re excited to share our vision with you soon.

Ok, that’s enough preamble. Let’s begin 🙌

Ilya Hardzeenka is principal architect at Vonage on a ‘how-to’ 'architecture series. Excerpt from his first post.

—

There’s a moment in many engineering careers when the question changes.

At first, you want to know how to become better at a language, a framework, or a stack. You compare Java and .NET. You read about Rust and Python. You care about which tool is faster, cleaner, more elegant, or more future-proof.

Then something shifts.

You are in a meeting about a release that is already slipping. The code is not the real problem. The handoff is. The deployment pipeline is brittle. One team owns the API, another owns the infrastructure, and nobody wrote down the decision that created the bottleneck in the first place.

That is when the question starts to change.

You stop obsessing over the tool itself and start caring about the shape of the system, the people who build it, and the people who depend on it. You begin to see that architecture is not a promotion badge or a job title.

Architecture is a responsibility under constraint.

That is usually when you are getting close.

Susanne Kaiser, author of "Architecture for Flow," shows how to combine Wardley Mapping, Domain-Driven Design, and Team Topologies into a single coherent approach. In this way your architecture, your teams, and your business strategy finally move in the same direction.

Some upcoming events to check out for architects, team leads, and engineers.

Stay chill,