3 ms·
My first boss had the title 'architect', but he was actually very competent, and very regularly got his hands dirty coding. (But at the time, I basically joine
by eru 2y ago
My first boss had the title 'architect', but he was actually very competent, and very regularly got his hands dirty coding.
(But at the time, I basically joined what was still essentially a startup just after they had been acquired by a larger company. I think the titles like 'architect' might have come from the larger company, but the competence came from them still being the same people as at the startup.)
- eropple 2y agoI'm currently at a very large company, and architects are, in many lines of business, the only technical folks directly employed by the company. Which means a product's quality hinges pretty directly on whether your architect is somebody technical who can help solve problems both at the implementation level and before they get to the implementation level (which I certainly try to be, when not triple-booked on meetings trying to keep everything else on the rails) or the Dilbert version. We do exist, I promise. ;) But in my case at least, the Eye of Sauron can only keep so many things in sight at a time...