4 ms·
I'd agree. Also, "architects" have also been rebranded as "staff" or "principal" engineers at some companies. (The cynical view is this because nobody archite
by icedchai 4y ago
I'd agree. Also, "architects" have also been rebranded as "staff" or "principal" engineers at some companies. (The cynical view is this because nobody architects a system with "agile", they just do what works for now and fix it in the next sprint.)
- hobofan 4y agoI think that's also because the past divide of "architects" and implementers (often in outsourcing settings where the architecting is done on-shore), is recognized to not work well. From my experience job descriptions/title that lean into "architect" tend to attract people that can theorize about how software ought to be built all day, but haven't written a single line of code in ages.