Thanks, shits been getting worse recently when the architect joined, and took things in his own hands at one point and told somebody he was talking shit. The architect was right, but was instantly ignored afterwards. which is why i asked the company to look for a new project because fuck that. And seeing the architect agreeing with me made me realise how bad it was and that what i thought wasnt wrong.
Either case, i learned from this project that some product teams can not be changed and its better to say fuck it.
Up to better moments and share our knowledge and ways with people that do care!
Good point about the ci/cd and i think i need to start asking that question in job interviews!
Once business/product start dipping their hands into the How, “I know how to design this” you know you’re cooked on the team. That’s what got me too, some manager who had probably 6 months of coding experience and then went into management was trying to tell me with 12 years of experience how I should architect. They’ll constantly lie to you convincing you that you’re the wrong one, when you have all of that experience
It doesn’t even make sense to hire a full time architect unless you’re constantly producing new solutions.
You could make an argument that an architect can intervene when existing products aren’t optimal but those skills should be in the domain of whatever senior developer you have lying around
The architect was brought in to make designs for code and solutions. He was not only a solution architect but also a design architect. And also, im the senior developer that did (i no longer give a fuck) what you said :p
The architect just happened to be in the meeting when one of the discussions broke loose hehe
Thanks, shits been getting worse recently when the architect joined, and took things in his own hands at one point and told somebody he was talking shit. The architect was right, but was instantly ignored afterwards. which is why i asked the company to look for a new project because fuck that. And seeing the architect agreeing with me made me realise how bad it was and that what i thought wasnt wrong.
Either case, i learned from this project that some product teams can not be changed and its better to say fuck it.
Up to better moments and share our knowledge and ways with people that do care!
Good point about the ci/cd and i think i need to start asking that question in job interviews!
Once business/product start dipping their hands into the How, “I know how to design this” you know you’re cooked on the team. That’s what got me too, some manager who had probably 6 months of coding experience and then went into management was trying to tell me with 12 years of experience how I should architect. They’ll constantly lie to you convincing you that you’re the wrong one, when you have all of that experience
It doesn’t even make sense to hire a full time architect unless you’re constantly producing new solutions.
You could make an argument that an architect can intervene when existing products aren’t optimal but those skills should be in the domain of whatever senior developer you have lying around
The architect was brought in to make designs for code and solutions. He was not only a solution architect but also a design architect. And also, im the senior developer that did (i no longer give a fuck) what you said :p
The architect just happened to be in the meeting when one of the discussions broke loose hehe