Darrell Norton's Blog [MVP]

Sponsors

The Lounge

News

  • Darrell Norton pic

    MVP logo

    View Darrell Norton's profile on LinkedIn

    Currently Reading:

    weewar.com

Advertisement

Images in this post missing? We recently lost them in a site migration. We're working to restore these as you read this. Should you need an image in an emergency, please contact us at imagehelp@codebetter.com
You don't need an ego to own the product

Jeff Atwood has an interesting post where he states that developers have to own the product. While I agree with it, his reasoning to get there seems a little off. He starts of by saying that developers should have an ego (and a big ego is somewhat implied), and he quotes Robert Glass from Facts and Fallacies of Software Engineering:

"Consider the notion of an egoless manager. That idea, of course, is preposterous! The ego of the typical manager is the driving force that makes him or her effective."

Robert Glass makes this statement with nothing substantial to back it up. The whole proof is the absurdity of the thought of it. Galileo ran up against the same argument, roughly paraphrased here, "Consider the notion that the sun is the center of the universe. That idea, of course, is preposterous!" Where are the facts? Don’t get me wrong, the facts part of Glass’s book is good because it has all sorts of, well, facts, but this fallacy is 100 percent opinion. The same argument can be used for whatever you don’t want to consider. “Consider the notion of college without beer. That idea, of course, is preposterous!” People that had fun in college are nodding their heads right now.

From there Jeff derives an ego-driven ownership. Somehow that’s confusing ego with ownership. Having an ego, even an inflated ego, is not the same as being the owner of something important. Although there is often correlation, there is no causation. And the idea of egoless programming in no way diminishes ownership of the end product. I think the problem is taking egoless programming to the extreme, which I agree does not work. Of course, most things taken to the absolute extreme don’t work too well in practice, but they do serve to counterbalance the opposite extreme.

So while I agree with Jeff, his argument doesn’t really work for me.


Posted Tue, Feb 22 2005 7:14 AM by Darrell Norton
Filed under:

[Advertisement]

Comments

Sahil Malik wrote re: You don't need an ego to own the product
on Tue, Feb 22 2005 7:27 AM
Ego is the mostest harmfullestest thing to any facet of your life or anything you might be associated with. It's so awful, a yeti's dirty ass is more desirable than an egotistic person.
Brendan Tompkins wrote re: You don't need an ego to own the product
on Tue, Feb 22 2005 9:21 AM
Ha! This is really funny. All bloggers, by default, are egoists! It's just how you express it, and how humble you can be as well. Ego != Asshole

We should all admit that we're ego driven. Get that out of the way. Then, we can really be effective communicators.

:)
Brendan Tompkins wrote re: You don't need an ego to own the product
on Tue, Feb 22 2005 9:21 AM
Oh, I'm gonna get shit for that one. :)
Darrell wrote re: You don't need an ego to own the product
on Tue, Feb 22 2005 9:47 AM
Hah. I would be remiss to say that I don't have an ego, it's one of the things I fight with every day. The important point is to not let it blind you. :P
Jennifer wrote re: You don't need an ego to own the product
on Tue, Feb 22 2005 4:15 PM
Ask Dave about ego. There's a difference between ego and ownership.

IS your ego getting in the way of coding better? If so, developers should tame the ego. I can the ego getting in the way of listening.
Jennifer wrote re: You don't need an ego to own the product
on Tue, Feb 22 2005 4:15 PM
Ask Dave about ego. There's a difference between ego and ownership.

IS your ego getting in the way of coding better? If so, developers should tame the ego. I can imagine the ego getting in the way of listening.
Greg Postlewait wrote re: You don't need an ego to own the product
on Wed, Feb 23 2005 5:44 AM
Taking ownership, by its own virtue, implies ego will be involved. You want to do a good job because your name is associated with the product, the software is a reflection of ones-self. Ego will try and protect itself by going to greater lengths to ensure quality, thus avoiding embarrasment.

(I presently work in a shop where ownership is discouraged, so anything that goes wrong is always someone else's fault.)

That doesn't mean an ego should make you a prick.

I love to show off a great piece of code, showing style and elegance to solve a task. That is best shown off at a user group meeting where your peers can momentairly bow to your greatness, then kick you in the teeth when you don't know how to do X. Humility + ego is fine.
Brendan Tompkins wrote re: You don't need an ego to own the product
on Wed, Feb 23 2005 6:04 AM
Oh, and from Rory's Wiki-Dictionary thing, the correct term for blogging ego is "Blego"
Darrell wrote re: You don't need an ego to own the product
on Wed, Feb 23 2005 6:59 AM
Greg - I agree that ego + humility is fine. Jeff's post, however, discourages egoless programming as presented in the original article, which if you read it (maybe you already have), is basically humility + ego as you stated.