I don't think the GP is claiming they are separate fields. However, I would say they are separate modes of thinking and require different skill sets. For examp

I don't think the GP is claiming they are separate fields. However, I would say they are separate modes of thinking and require different skill sets. For example, software architecture around systems design might involve thinking of different layers of responsibility, the sequentiality of development, taking into account the skillsets of the teams and existing technical tools and structures. To me, programming is the art of transforming and ascertaining requirements and principles into executable structure. Architecture is the art of shaping the non-functional requirements and principles. Either by writing them down or by discussing them at a whiteboard, or even by teaching the team about these requirements. Both are like an entangled pair that can be incorporated in one single individual, in different team members or even in different organisational structures. Some architectural decisions can be championed by a random software developer. Some architectural decisions shape companies (AWS). And some architectures should just be thrown out of the window. But, and I am speaking from experience here, as they are different modes of thinking, there should be conscious time and effort for both and they should not be mixed indiscriminately.