Earlier quoted context omitted.
Really? Because a Scrumaster or an agile project manager who doesn't post code immediately is irrelevant? That's an odd conclusion to make. It seems clear to me after reading several of his posts that he manages people. While it is certainly true that there are a subset of managers who are also PHBs, I don't think you could highly correlate those who are and those who aren't by the number of posts they make about wor…
> Why is it that people disparage managers who don't write about code? Because it increases the probability that they don't understand what they're managing. Look at Peter Norvig or Urs Hoelzle or Jeff Dean. They are still very, very technical despite managing many people. That earns them credibility among their troops. By contrast, this guy has written about 70 posts on Agile with almost zero code. I could find exac…
I don't like you very much
41–49 of 49 posts
Re: I don't like you very much
#42Earlier quoted context omitted.
> Why is it that people disparage managers who don't write about code? Because it increases the probability that they don't understand what they're managing. Look at Peter Norvig or Urs Hoelzle or Jeff Dean. They are still very, very technical despite managing many people. That earns them credibility among their troops. By contrast, this guy has written about 70 posts on Agile with almost zero code. I could find exac…
I agree that he's unlikely to be someone who would earn an engineer's technical respect. By any chance are there other competencies a manager of technical projects ought to have?
The first trait of a manager in high tech (whether professor or product manager) has to be technical competence.
That trait is not usually sufficient to be a good manager. But I think it's necessary (you seem to disagree?)
Re: I don't like you very much
#43Earlier quoted context omitted.
I agree that he's unlikely to be someone who would earn an engineer's technical respect. By any chance are there other competencies a manager of technical projects ought to have?
Sure, but now we're talking about a programmer analog of Maslow's hierarchy of needs. The first trait of a manager in high tech (whether professor or product manager) has to be technical competence. That trait is not usually sufficient to be a good manager. But I think it's necessary (you seem to disagree?)
I could see this being different in other environments (eg I can't imagine a research team manager not being an alpha geek) but for most corporate environments there are a lot of other skills I'd look for before technical competence.
For example, one of my inspirations early in my career was an EPM (engineering project manager in the company's lingo) who had zero technical background. What she did have was an amazing ability to listen to everyone involved in the project, pick out the chains of dependencies, negotiate schedules with us, follow up relentlessly on any open questions and summarize what we'd just said better than we ever could. She made a massive difference, and the team's productivity dropped like a stone when someone less talented took over.
Re: I don't like you very much
#44Re: I don't like you very much
#45Earlier quoted context omitted.
Really? Because a Scrumaster or an agile project manager who doesn't post code immediately is irrelevant? That's an odd conclusion to make. It seems clear to me after reading several of his posts that he manages people. While it is certainly true that there are a subset of managers who are also PHBs, I don't think you could highly correlate those who are and those who aren't by the number of posts they make about wor…
> Why is it that people disparage managers who don't write about code? Because it increases the probability that they don't understand what they're managing. Look at Peter Norvig or Urs Hoelzle or Jeff Dean. They are still very, very technical despite managing many people. That earns them credibility among their troops. By contrast, this guy has written about 70 posts on Agile with almost zero code. I could find exac…
Agile can be two things. It can be a development methodology and it can be a project management methodology. Being good at one does not imply being good at the other. I work with people who are geniuses at managing agile projects but that couldn't code their way out of a shoe box with 3 sides cut out. It's their ability to manage that is important, not their technical chops.
Re: I don't like you very much
#46Earlier quoted context omitted.
There's a trick here. At the surface it sounds naive, sure. The trick is that people can and should passionately defend and believe in the viewpoints, espouse and defend them, and then go along with what the group decides. Either "passionately defending" or "going along" is not sufficient in itself. You have to have both.
There's a phrase for this, it's known as having Strong beliefs, weakly held .
I'm stealing that one. (grin)
Re: I don't like you very much
#47I've never met the guy and I don't like him.
Honestly? Would you actually go up to him and say "I don't like you" if you saw him, or are you just being an Internet Tough Guy?
I don't randomly walk up to people and discuss my opinion of them. But if someone started a conversation with me about how many people do or don't like them then yes I would have to tell them I find them irritating and walk away. There is nothing 'tough' about it.
Nor am I an Internet tough guy, just giving an opinion is all I'm doing. People that obsess over who like them or not and why, I just don't like them.
Re: I don't like you very much
#48Earlier quoted context omitted.
I didn't do anything except post here, so I assume it's a feature of that blog.
I thought you had a great comment, so I manually entered it. My article had a lot of logic and tone problems which you pointed out. I thought readers of the blog should see your comments. Let me know if this bugs you and I will remove it.