- You always talk about the big picture.
- You think you know how the system ought to be built.
- You are unhappy that the team is not executing your ideas the way you want them.
- You don’t have a working build.
- You spend a lot of time on documents that are not code.
- You can prototype – but your code is not production worthy.
- You spend too much time in meetings.
- The best code you wrote is a few years old.
- When asked for opinions you tend to speak in general terms.
- Your team members secretly joke about you.
- You start to take analysts and tech blogs too seriously.
- You are a dinosaur.
Code. Don’t wiki. Don’t powerpoint.
{ 201 comments… read them below or add one }
← Previous Comments
Next Comments →
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/6O9tdtnx << “If you want to be an architect, you better be the best in the team.”
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
“@Carnage4Life: Architect: Overrated! – http://t.co/X4kJx1Pp #programming” :)
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/KZIaGFeq #programming
@Carnage4Life: Architect: Overrated! – http://t.co/cXu4oXjF #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
Architect – Overrated! http://t.co/iV5M09iM
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @codinghorror: RT @Carnage4Life: Architect: Overrated! – http://t.co/WOa6miay #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
“@Carnage4Life: Architect: Overrated! – http://t.co/m64mxTZr #programming” /cc @mcsnootch ;)
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
please note that i didn’t say it. this time. http://t.co/L4LPmTRP “#architect” #fb
Esto describe perfectamente a casi todos los arquitectos en el mundo de las consultorías de software http://t.co/fABsi7zQ via @codinghorror
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
While I appreciate where these feelings come from, I think you would be better served by spending your obviously well tuned brain cells to the problem of…
“How do I improve my relationship with my architect?”
I certainly hope you emailed him this link to your post.
While in the vast majority of cases I agree. On large projects however they are needed to counteract 1st line engineering managers. Who often have their team deliver and work on only tasks that the manager has been assigned as deliverables. Which is often in conflict with what’s needed for the project to succeed. Like the task x that nobody committed too but is critical. Or the managers agreed on an illogical partitioning of tasks.
It can also be useful to have a technical track for developers that has levels up the Director or VP level. Not just for career growth but also for escalating serious technical issues up above any territorial engineering manager dispute, which happen more and more as the project size increases. There’ nothing worse than a whole group of 1st line engineering managers who all successfully completed all their tasks lists on time and boom a six month slip. Especially when the developers knew it would happen the whole time.
You see these issues with really large releases like operating systems. Not so much with small teams. Nothing worse than breaking your but for six months on a project you know is doomed.
LOL, so true with some S/W architects! RT @Carnage4Life Architect: Overrated! – http://t.co/cOaItWZN #programming
Architect – Overrated! http://t.co/U3zSTJTI
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
It’s critical to have an initial design that is well baked as they say. When you have lots of groups from vastly different technical backgrounds working it can be difficult. It sometimes comes down to what unknowns/risks you are willing to accept. I’ve seen at least one project completely fail due to issues that could have been pointed on day one. But that was just a bad job or probably more a case of someone not realizing that they didn’t have the background to lead the design for that project.
And I’m a C/C++ developer who has delivered at least one subsystem on every release I’ve worked save one. And I was switched to that project after it slipped and was forced to be the release manager (and I still fixed bugs).
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
Architect – Overrated! http://t.co/cIh09foi
And if your still not convinced in the importance of good technical leadership… I worked at one company that would develop or buy two versions of the same product. By different teams of people, group A and B. Then after evaluating various metrics like performance, maintainability, performance against schedule, ease of adding new features, sales/customer feedback would choose a winner. Say group A. They they fired the entire “losing” team, group B. Which team would you want to be on? The one with good experienced technical leadership or the one where you had to hope that your engineering manager didn’t do performance reviews based on but kissing?
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
I am NOT that kind of architect. I code! RT @Carnage4Life: Architect: Overrated! – http://t.co/02L2RIOj #programming
RT @Carnage4Life: Architect: Overrated! – http://t.co/JdwElDyN #programming
← Previous Comments
Next Comments →