Not always. In some cases you create little prototypes or examples or partial implementations of various components, and then hand those off to the person or persons who will do the full implementation.
And then they will completely fuck it up because they didn’t want to follow your example and/or they don’t know how to read or communicate. And then you have to go and debug their stupid bullshit.
And then they will completely fuck it up because they didn’t want to follow your example and/or they don’t know how to read or communicate. And then you have to go and debug their stupid bullshit.
Alternativelly and having had the software architect responsability myself and also been on the other side, they fuck it up because they didn’t know how to properly communicate with people who can’t read their fucking mind, they didn’t do a specification with the smallest possible number of insufficiently defined elements and they did not maintain open communication with the implementation team for the invariable parts of the specification that turn out to not have been defined with enough depth or collide with the reality of what’s possible.
IMHO, ultimatelly is the responsability of the senior person to figure out how much hand-holding the implementation team needs and adjust to them, rather than expect that for example a bunch of Junior Developers can just get a specification that consists a bunch of examples (or the other equally bad format for them: the massive wall of boring text) and not fuck it up.
In my own career I’ve seen far more people with Technical Architecture responsabilities (and even the title) that did not know what the fuck they were doing, than seen Junior and Mid level Developers that were below what is expected of somebody at that level of their career.
This guy architects. You also get to a spend a lot of time explaining to non technical folks why their ideas are bad or expensive to build. Lots of being the bad guy.
Not always. In some cases you create little prototypes or examples or partial implementations of various components, and then hand those off to the person or persons who will do the full implementation.
And then they will completely fuck it up because they didn’t want to follow your example and/or they don’t know how to read or communicate. And then you have to go and debug their stupid bullshit.
Alternativelly and having had the software architect responsability myself and also been on the other side, they fuck it up because they didn’t know how to properly communicate with people who can’t read their fucking mind, they didn’t do a specification with the smallest possible number of insufficiently defined elements and they did not maintain open communication with the implementation team for the invariable parts of the specification that turn out to not have been defined with enough depth or collide with the reality of what’s possible.
IMHO, ultimatelly is the responsability of the senior person to figure out how much hand-holding the implementation team needs and adjust to them, rather than expect that for example a bunch of Junior Developers can just get a specification that consists a bunch of examples (or the other equally bad format for them: the massive wall of boring text) and not fuck it up.
In my own career I’ve seen far more people with Technical Architecture responsabilities (and even the title) that did not know what the fuck they were doing, than seen Junior and Mid level Developers that were below what is expected of somebody at that level of their career.
Synonym for Cloud Architect would be IT Project Manager. :)
It’s one of those inflated titles that doesn’t actually mean what the words by themselves would mean.
This guy architects. You also get to a spend a lot of time explaining to non technical folks why their ideas are bad or expensive to build. Lots of being the bad guy.