I am going to try to take the architecture out of architecture. I am not sure it is possible to define what architecture is or what architects do. The term is just too vague.

I am going to try to do it the same way we pull services out of monoliths, just making new, smaller, better terms (or actually, more like taking the ones that are out there and pulling them out of the architecture-monolith)

I think I want to start easy, something maybe saying the SRE is not architecture, maybe it is well defined enough to live its own life outside the vague definition. That should include stuff like monitoring for performance, errors etc.

Following that way of killing the term architecture, one definition after another, maybe we can get rid of architects once and for all. And end use things like "Domain modelling", "SRE", "Infrastructure" etc.

There used to be terms like "Application architecture" and "Information architecture" etc, they just seem very dated definitions by modern software development standards and we probably need new ones.

At least now, when I sometimes do domain modelling and sometimes do SRE-type-stuff, it just seems silly to talk about it as the same things. It is not even close to the same skillset (I enjoy doing both, for sure, but not talking about it as the same thing).

Also, I am not sure I want to try to do it generic, like for all. I think I would like to do it mostly for our own org. Like, what are the things we do that we struggle to find names for.