Yeah, I can relate. I've been doing consultant work and I always tried to avoid being pushed into the "architect" role. My background for over 25 years was software development and we had a lot of success with agile methods (doing it right is hard but viable and it produces quality software) My experience is that a good dev team does not need an "architect" to tells them what's best. But all of this is now gone anyway, or at least taking an extended break. At the moment no one is investing in development teams, and the prospect of being able to fire all the developers because AI can do their job now is making CEOs giddy everywhere. Not going to happen (and this should be obvious for anyone who can judge the quality of code or the effectiveness of processes in terms of reliability, quality, cost, performance etc.) but that doesn't stop them from trying.
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
replies: