3 ms·

You always see this at the top of every list of this general ilk. For me, it's true. I do it and I love it. But when I look around the office at my co-worker

You always see this at the top of every list of this general ilk. For me, it's true. I do it and I love it. But when I look around the office at my co-workers, I honestly believe 70-80% of people would either just abhor it or be terrible at it. Even though they might complain about it, they love meetings. Love them so much. They get out of a meeting and genuinely feel like they did something productive. These people would be deeply unhappy if they were yanked out of the candyland where having meetings and opinions was what they were responsible for and suddenly were told "Now you have to do something tangible to earn a living." ... In the same way I would be deeply unhappy if I were told I had to go to meetings all day. The point is, this probably is the best job... but not for a lot of people. So it seems misplaced at the top of all these lists.

mastazi 12y ago
As a developer, "meetings" and "expressing opinions" is exactly how I picture a software architect's job. I'm not saying that in a diminutive way, I actually think that interpersonal communication and group work are very important in any human endeavour.
- mastazi 12y ago
  ...and I wish I could spend more time exchanging ideas rather than staring at my IDE.
- vendakka 12y ago
  There is usually a fair bit of prototyping work involved as well. There's also a lot of listening involved, as you can't really design a good system without first talking to the people who are going to use the system and understanding their needs. In addition you'll need to listen to the folks who are going to be implementing the system as well so you get a feel for what they are good at and what they enjoy working on.