I think in many organization, developer have been strip off many of the responsibility and are only expected to "translate" requirement into code. Thus many of us stopped being interested in what was part of our job (business, architecture...) leaving the responsibility to someone else.
This make us believe that we are only writing code and forget that any decision we made will have a impact at some point
It goes hand-in-hand with waterfall & siloed organizations - to have phases & responsible people: requirements (BA), architecture (architect), coding (developers), testing (QA), release (operations engineer)...
The key problem is the feedback loop. Architects might spend months designing the "best" design, Developers might spend months implementing that "design"... and even when it's discovered that the design isn't suitable, people see it as "too late" to say/change anything (and often there's a power imbalance between those architects and developers, and we have the sunk-cost fallacy too)
Architect isn't a job title.
Exactly, we need to move away from silos.
I think in many organization, developer have been strip off many of the responsibility and are only expected to "translate" requirement into code. Thus many of us stopped being interested in what was part of our job (business, architecture...) leaving the responsibility to someone else.
This make us believe that we are only writing code and forget that any decision we made will have a impact at some point
It goes hand-in-hand with waterfall & siloed organizations - to have phases & responsible people: requirements (BA), architecture (architect), coding (developers), testing (QA), release (operations engineer)...
The key problem is the feedback loop. Architects might spend months designing the "best" design, Developers might spend months implementing that "design"... and even when it's discovered that the design isn't suitable, people see it as "too late" to say/change anything (and often there's a power imbalance between those architects and developers, and we have the sunk-cost fallacy too)
I've seen this pattern multiple times. People get so use to it that they forget other way of working exists
Yes exactly. They are rewarded by perfoming in their role, even though the whole process is suboptimal - local instead of global optimization.