5 ms·
Aside - Why do we need the word "architecting" anyway? Why not just use designing?
by gashmol 1y ago
Aside - Why do we need the word "architecting" anyway? Why not just use designing?
- leecommamichael 1y agoArchitecting at least somewhat harkens to engineering; where there are costs, limits, tolerances, and to some degree aesthetics.
- gashmol 1y agoI'm pretty sure every engineering field calls it designing. Perhaps software devs feel a need to inflate what they actually do.
- corytheboyd 1y agoIn my (software) experience, the terms are basically interchangeable. Some people will violently defend “architect right, design wrong” and others the opposite, So uh, pretty hard for me, a normal person, to care much about which word is right for the “you sit down and think before you build” part of software engineering.
- bsoles 1y ago> the “you sit down and think before you build” part of software engineering. Well, Agile, Scrum, and backlogs took care of that. /s
- toolslive 1y agoIn my country, we have both the academic title "engineer", and "engineer architect". People view this as "proper engineer" and "not so proper engineer". Anyway, "you sit down and think before you build" is indeed what you want and the word for that is "strategy".
- degamad 1y agoI think the analogy is to construction, not engineering. In construction, architects and designers do different jobs. The software equivalents of those roles map reasonably well to the construction equivalents.
- layer8 1y agoSoftware architecture is about the higher-level, big-picture stuff: https://stackoverflow.com/a/704909/623763 https://stackoverflow.com/a/704909/623763
- toolslive 1y agoDesign and architecture are 2 different things. Design is about appearance. Architecture is about structure.
- layer8 1y agoSoftware design [0] isn’t about appearance. [0] https://en.wikipedia.org/wiki/Software_design https://en.wikipedia.org/wiki/Software_design