Ask HN: Is the architect role less demanded in software than before?
I've noticed an apparently decrease in opportunities and offering on training and courses or other material focused specifically in architects. I've had less contact with them in recent job experiences than 10 or 15 years before. I suggest a couple of possible reasons: Maturity in software practices inside companies, more autonomy between developer teams, Agile put aside the heavy documentation paradigm, speciality in software that lead to diversify responsabilities in new areas like devops and data analysis, and new roles like Principal and even the Senior developer. Do you consider this is real or just a bias from my own experience?
I’m always been very skeptical of software architects. Ideally, any software engineer with more than 10 years of experience should know enough and have the enough experience to be a decent architect. A team of 2 or 3 of these seniors won’t need the help of a dedicated architect.
As an Architect, i'd say my role is more Principal/Staff Eng these days. I spend at least half my week coding (which is great!)
Whilst i'm ultimately accountable for the Architecure to c-suite (i.e. ensuring it meets NFR's etc) we, as the team, are collectively responsible for it, and we own the decisions.