Software Architecture: It Might Not Be What You Think It Is

infoq.com

37 points·rbanffy··7 comments

Architecture is that which drives the configuration of the system's block diagram. That block diagram is the "building" and the architecture metaphor comes from the idea of how things are connected: is there an external stairway from here to there, or an elevator? Are these two facilities on the same floor?

Saying that architecture isn't structure but decisions is vacuous fluff, because a structure has decisions. A triangle and square are structures, differentiated by the decision of how many vertices/edges we have.

Decisions that don't result in structure might not be architecture. Soup vs. salad is a decision, but doesn't mean you're architecting your lunch.

Well said.

The fact that "Architecture" is merely a manifestation and documentation of "Systems Thinking" seems to have escaped them. You definitely need one or more people playing the Role of an Architect (i.e. keep the entire big picture together) in any team.

The Software architect is the most important person on the project because there’s no point in building two halves of a bridge if they’re not going to end up meeting in the middle

> Architecting is a skill; Architect is not a role

> His past roles include serving as Chief Enterprise Architect

Ahhh yes, the legendary: chief executive enterprise Senior architect consultant VP engineer.

It’s strange how these people only work at a company size of like one or two though

A company of size of one or two, is not an enterprise (in any meaningful sense related to EA), so that would be logically flawed.

It’s a joke, just like a lot of peoples resumes unfortunately.

Reply on news.ycombinator.com