4 ms·

I diasgree. An architect usually doesn't develop. I suggest you google architect (solutions, systems, application, network ...etc).

by guiomie 13y ago

Spearchucker 13y ago
The first link that search returns is solution architecture from Wikipedia [1]. In "Overview of solutions architect", second paragraph: A practitioner of Solution Architecture, Systems engineering and Software engineering processes, the Solutions Architect is... I've been writing code for over 20 years, and have been an architect (I dislike that title as much as I do full-stack dev) for 14 of those. If you tell me you're an architect that doesn't code, you lose credibility (with me). Network architecture might involve scripting or code but is predominantly about configuration [2]. It's simply an infrastructure stream as opposed to a dev stream. [1] http://en.wikipedia.org/wiki/Solutions_Architect http://en.wikipedia.org/wiki/Solutions_Architect [2] http://www.wittenburg.co.uk/Entry.aspx?id=91035731-e5b6-491d-8d0a-1a8b6da293e7 http://www.wittenburg.co.uk/Entry.aspx?id=91035731-e5b6-491d...
- Silhouette 13y ago
  If you tell me you're an architect that doesn't code, you lose credibility (with me). It's an overloaded term these days, and things like "information architecture" are very different to "software architecture", so I wouldn't put it quite as strongly as you did there. That said, I agree completely with the point I think you were really making. To me, a software architect is just a senior developer who has particular responsibility for big picture and integration issues, possibly along with other development roles they play. It's the breadth counterpart to a technical lead, who is a senior developer with particular responsibility for specific parts of the system and a deep understanding of those parts. IME having a software architect becomes useful somewhere around the time that anyone on your team can no longer talk to anyone else just by swivelling their chair and saying hi. They don't have to have the word "architect" in their job title, but somebody had better be making sure that Andrew, Bill, Claire and David are all writing code that's going to fit together in a maintainable way and that the tools are there to build and test the combined code.

I diasgree. An architect usually doesn't develop. I suggest you google architect (solutions, systems, application, network ...etc).

by guiomie 13y ago

I diasgree. An architect usually doesn't develop. I suggest you google architect (solutions, systems, application, network ...etc).

Spearchucker 13y ago

The first link that search returns is solution architecture from Wikipedia [1]. In "Overview of solutions architect", second paragraph: A practitioner of Solution Architecture, Systems engineering and Software engineering processes, the Solutions Architect is... I've been writing code for over 20 years, and have been an architect (I dislike that title as much as I do full-stack dev) for 14 of those. If you tell me you're an architect that doesn't code, you lose credibility (with me). Network architecture might involve scripting or code but is predominantly about configuration [2]. It's simply an infrastructure stream as opposed to a dev stream. [1] http://en.wikipedia.org/wiki/Solutions_Architect http://en.wikipedia.org/wiki/Solutions_Architect [2] http://www.wittenburg.co.uk/Entry.aspx?id=91035731-e5b6-491d-8d0a-1a8b6da293e7 http://www.wittenburg.co.uk/Entry.aspx?id=91035731-e5b6-491d...

Silhouette 13y ago
If you tell me you're an architect that doesn't code, you lose credibility (with me). It's an overloaded term these days, and things like "information architecture" are very different to "software architecture", so I wouldn't put it quite as strongly as you did there. That said, I agree completely with the point I think you were really making. To me, a software architect is just a senior developer who has particular responsibility for big picture and integration issues, possibly along with other development roles they play. It's the breadth counterpart to a technical lead, who is a senior developer with particular responsibility for specific parts of the system and a deep understanding of those parts. IME having a software architect becomes useful somewhere around the time that anyone on your team can no longer talk to anyone else just by swivelling their chair and saying hi. They don't have to have the word "architect" in their job title, but somebody had better be making sure that Andrew, Bill, Claire and David are all writing code that's going to fit together in a maintainable way and that the tools are there to build and test the combined code.