“Software architect” is out of fashion “architect” implies “design (mostly) before building starts” We need design in software dev, design that never stops
99
160
31
1,156
Replying to @jessitron
100% of all software architects that deserve the label would agree that “design (mostly) before building starts” is the wrong approach, and that architectural work is something that needs to happen throughout the lifetime of a system

Sep 25, 2021 · 7:58 PM UTC

9
18
1
145
Replying to @stilkov @jessitron
Architecting should happen throughout the life of an application. But from the moment it comes into existence, an application has an architecture whether or not you have explicitly chosen it. Best to do some small, upfront architecting...
1
3
1
19
Replying to @stilkov @jessitron
Design happens always, even when you're not building.
4
Replying to @stilkov @jessitron
But then what do all the Power Point solution architects do? 😂
1
Replying to @stilkov @jessitron
true, but 90% of the software architects in enterprise companies wouldn't agree....
1
Replying to @stilkov @jessitron
To me architecture is a puffed up term for design. And I think that you design is more important than the question of when you do it. It is software after all, there is no basement to get right before adding floors and a roof.
1
1
Replying to @stilkov @jessitron
etymonline.com/word/architec… - "from Greek arkhitekton 'master builder, director of works,'", sounds pretty accurate to me.
1
Replying to @stilkov @jessitron
Couldn’t agree more, great software architects sketch then build, but they always THINK before they build. Too many developers code THEN think.
1
11
Replying to @stilkov @jessitron
And since best architectures are created by teams, architect is just team member(s) without any special privileges, making the role obsolete.
3
Replying to @stilkov @jessitron
Having a general idea what you are going to build before starting helps in the long run as well.