There are so many myths about software architecture ... * that it's done once and there's no further cost associated * that if you do it properly, it will serve forever * that there's "the correct way to do it" & you measure correctness with "software architecture" aesthetics There's one more I find especially irritating:...
Quite recently I've shared my personal interpretation of "seniority" in tech (based on the concept of "leverage" - shamelessly stolen from Andy Grove ...). This term ("seniority") is frequently closely associated (as an enabler) to the role of an "architect" - which is another topic I use to share my thoughts...
I tend to observe interesting trend, appearing one and then here and there - people overuse the words "architect" and "architecture" when they speak about software: * every diagram is "an architecture blueprint" * every design document is "an architecture overview" * every analyst who creates a high-level design document is a "solution...
