A few of us were sat in the pub the other night and started discussing the difference between a lead developer and an architect. Specifically, we were trying to get to the bottom of when it feels right to call yourself an architect.
My first take on this was experience and confidence. I think the key thing that differentiates an architect from a lead developer is experience. That is, experience across many systems and many different types of solutions. Where confidence comes into play is that you need to feel confident in your experience to feel comfortable to call yourself an architect. What do you think? Let's try to continue this online.
Simon is an independent consultant specializing in software architecture, and the author of Software Architecture for Developers (a developer-friendly guide to software architecture, technical leadership and the balance with agility). He’s also the creator of the C4 software architecture model and the founder of Structurizr, which is a collection of open source and commercial tooling to help software teams visualise, document and explore their software architecture.