upvote
Agreed, and another point that I haven't seen in the article : 'architect' as a separate software engineering role was a bit of a bad word, even if everybody agreed that architecture was important.

It was mostly because in some companies there was a cast of 'architect' who were seen as above coding, and who mostly delivered out of touch UML diagrams, or ill-fitting data-structure. The core of the issue was that even good programmers would rust and get incapable of understanding the ground truth if the organization discourage them to also be in the implementation side.

Here it's not exactly the same thing with AI, since the loop is dramatically shorter, but the (lack of) feedback issue remains.

I really believe that my added value as a programmer was fundamentaly to evaluate technical tradeoff of the different options to solve a business issues, and them to implement them. Now with Claude code I'm infinitely faster at the implementation part, but I'm also eroding my capacity to evaluate those tradeoff.

Programming is a medium, and you also need to work with it from time to time in order to keep some level of competency. And yet in many companies we are basically forbidden to do that.

I feel that we have been given cars, but have also been forbidden to ever walk again; Sure the car is more efficient most of the time, but there's a an almost-vital reason why we have to do jogging to compensate.

reply
It is still present tense for architects, hence Technical Architect, Solution Architect, Business Architect role variants.

And yes walking is refreshing and should not be taken away.

reply
But during that time the number of software engineering and development jobs and compensation levels continued to increase.
reply
Where outside startup scene?
reply
> each team only needs a single architect

Are they peer reviewing themselves? Who's pushing back on their ideas and decisions?

reply
Usually the developers, which are now a bunch of agents instead.
reply
[flagged]
reply