4 ms·
Why is "skilled engineer" better than "architect"? They are all just names - and it seems that the main reason people avoid the word "architect" is just because
by dack 14y ago
Why is "skilled engineer" better than "architect"? They are all just names - and it seems that the main reason people avoid the word "architect" is just because it has been abused in the past (and for some companies, the present). Maybe that's valid, because using the term may inadvertently make someone think that you're bought into the "no coding, but telling other people how to code" mindset.
However, I don't think "architect" is a silly name on it's own - it's just another piece of vocabulary we use to describe a certain role. It's no different to me than "VP" or "Janitor" or "Test automation engineer".
- codeonfire 14y agoArchitect, chief engineer, principal, fellow. These all mean 'put out to pasture'. These are supposed to be positions of leadership, but with no direct reports there is no one forced to follow. Developers who already have to deal with the business bureaucracy are not going to listen to someone because of a fancy title that does more politicking than development. Plus architect gives the image of a scarf wearing drama queen who throws tantrums.
- mikeflynn 14y agoIn my experience that architecture roles can definitely mean that at a lot of companies (the pasture part specifically, but I would like a scarf). To some degree it's natural to let the role end up like that, but as the person in the role, you have to work to make sure you're still involved with all teams even if you don't have any direct reports.