in reply to Please remember that geeks have their own social mores.

Back in school there were some people who thought it was normal to be bad at math, and even boast with it. I never liked them, and I don't think many geeks like these people.

I think we should apply the same standards to social skills: it's nothing to be proud of if you're bad at, and it's not god given (you can learn socials skills, yes).

BTW developers mostly write their software for users, so they should accept users as important, even seemingly stupid users.

  • Comment on Re: Please remember that geeks have their own social mores.

Replies are listed 'Best First'.
Re^2: Please remember that geeks have their own social mores.
by dragonchild (Archbishop) on Feb 21, 2008 at 16:26 UTC
    I think we should apply the same standards to social skills: it's nothing to be proud of if you're bad at, and it's not god given (you can learn socials skills, yes).

    Yes, social graces are important. The difference is that the developers I care to work with don't make it #1. It's more like #4 or #5, unlike most other people.

    BTW developers mostly write their software for users, so they should accept users as important, even seemingly stupid users.

    I don't. I write software cause it's fun. That people are helped out is a neat side-benefit.


    My criteria for good software:
    1. Does it work?
    2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
      I write software cause it's fun. That people are helped out is a neat side-benefit.
      And what fun means for you? For differnt people it means different things - but some would find helping others as fun. I think it is a very important question - because really big part of Open Source software is produced because it is fun for the developers. I have just started reading 'The Theory of Fun' - I'll add here something when I finish it.
        Just what it means - fun. I enjoy the creative and problem-solving aspects of programming. I enjoy "beating myself" and making better software every time. I enjoy stretching my brain. That I get paid for it (and paid very well) is a really freaking cool side-benefit. But, I suspect that I would write software on the side even if I drove a truck for a living.

        My criteria for good software:
        1. Does it work?
        2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?