3 ms·
> he had in excess of 15 years of experience From your description, it looks like the code was optimized to irritate while remaining functional. Might he have
by ur-whale 6y ago
> he had in excess of 15 years of experience
From your description, it looks like the code was optimized to irritate while remaining functional.
Might he have been pissed with the institution he worked for?
- jlengrand 6y agoNo, I think he really tried his best, working more than 55 hours / week towards the end. He had been an architect for more than 10 years in a large corp, and joined this small company I joined too. I think the expectations, lack of coding practice for a few years, architecture jargon that made him seem like an expert was a recipe for disaster. Not completely his fault.
- carlmr 6y ago>He had been an architect for more than 10 years in a large corp, and joined this small company I joined too. A lot of "software architects" are just people that have been at a big corporation long enough that they found someone willing to promote them, but they don't have social skills to put them in a managerial role. In my experience it often also means they stop coding and only do presentations and (bad) UML Diagrams. Leading to the complete deterioration of their skills.
- jlengrand 6y agoWell, I'm not the one who said it. I have met some architects that were a crucial part of the company. I have also met exactly those that you mention. And arguably they get promoted because they do less harm there than in a team of developers. . .