public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
To: "xconq" <xconq7@sources.redhat.com>
Subject: RE: Why Eric doesn't like my personal style
Date: Sun, 23 Nov 2003 14:22:00 -0000	[thread overview]
Message-ID: <OOEALCJCKEBJBIJHCNJDAEFKGMAB.vanevery@indiegamedesign.com> (raw)
In-Reply-To: <16320.9269.137384.122814@flacy.home.flacy>

Mark A. Flacy wrote:
>
> Brandon> He is somewhat correct, and I'm not going to change how I do
> Brandon> business for him.
>
> No doubt that's the secret to your success.

Do you want to define "success?"  You're working on a hobby project with
a small number of developers.  What do you know about "success" in game
development?  You some kind of principal at a well-known and
well-respected game company, just moonlighting here?

> Please find something else to do or simply DO something and
> shut the fuck up about it.

Well, it is true that I am looking around for codebases where I don't
actually have to convert people about what to do.  That are in better
shape from an OO and higher level functionality / make major changes
standpoint.  People like you make it easier not to worry about
"generosity" as one of the factors.  It's as though you think people
should just gladly do things for Xconq, without regard for basics like:

- whether anyone would actually use, desire, or test the Python code.

- whether it would actually get checked into CVS in any timeframe of
relevance to me.

Without even these basics, why would anyone with my priorities develop
anything for you?  Nevermind all the flat C code.  Sure it works, but in
2003 it's not an attractive development platform.  You know this; the
question is whether you have any energy to change it, or if you're
satisfied that "it's working for you."  If it works for you I don't
begrudge you that fact.  But it doesn't work for me, nor a lot of other
OO developers out there.  We simply couldn't do the things we want to do
in Xconq without changes to the infrastructure.  We are disinclined to
write major, painful buckets of C code.

FWIW the conversation with the Freeciv guys has been nicer, because I
had already gone over the personality land mines here and I didn't feel
the need to repeat them there.  I never expected the Freeciv guys to
change their ways, so I didn't set it as a goal to try.  Rather, I
thought I'd check to see if I might be pleasantly surprised, and I'd try
to understand something about why C coders stick to their guns.  Turns
out someone did do some Python once upon a time, and it fell by the
wayside.  Guess if you build it, people don't come eh?

Since you've seconded Eric's attitude, I'm outta here.  Some of you will
be glad; I'm glad, because at least it's a resolution.  What I've
learned from this experience, is team dynamics (or lack thereof) is as
important a factor as anything else.  Some kinds of people, with some
kinds of priorities, I simply cannot work with no matter how many
appeals to altruism or freeware do-goodery people might try to hide the
problems in.  What it gets down to, is you have your agenda, I have
mine.

"Thanks," at least, for helping me to clarify my agenda.  I'm pretty
clear on what it is now, this has been a good exercise for me, if not
for you.  And hey, you got VS 2003 files out of the deal, I've paid my
bar tab.  Next move is I'll either find a project that intersects with
my agenda, or I'll start my own.  Maybe I'll ping you guys about what
happens at some point.  Some of your lurkers I think would actually
prefer to work on something ala Python.


Cheers,                         www.indiegamedesign.com
Brandon Van Every               Seattle, WA

"We live in a world of very bright people building
crappy software with total shit for tools and process."
                                - Ed Mckenzie

  reply	other threads:[~2003-11-23 11:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20  2:15 Xconq UI thoughts Stan Shebs
2003-11-20  2:26 ` Brandon J. Van Every
2003-11-20  2:57   ` Eric McDonald
2003-11-20  9:45     ` growth agendas and OO Brandon J. Van Every
2003-11-20 10:49       ` Bruno Boettcher
2003-11-20 10:59         ` Brandon J. Van Every
2003-11-20 11:51           ` Jakob Ilves
2003-11-20 12:05             ` Brandon J. Van Every
2003-11-20 17:57             ` Jim Kingdon
2003-11-20 17:24       ` Eric McDonald
2003-11-20 17:51         ` Eric McDonald
2003-11-21  1:59         ` altruistic VS 2003 Solution files Brandon J. Van Every
2003-11-21  4:17           ` Eric McDonald
2003-11-21  9:02             ` So let's get right to the point Brandon J. Van Every
2003-11-21 23:14               ` Lincoln Peters
2003-11-22  0:06                 ` Why Eric doesn't like my personal style Brandon J. Van Every
2003-11-23 11:13                   ` Mark A. Flacy
2003-11-23 14:22                     ` Brandon J. Van Every [this message]
2003-11-22  0:07                 ` So let's get right to the point Brandon J. Van Every
2003-11-21  2:01         ` growth agendas and OO Brandon J. Van Every
2003-11-20 10:31   ` Xconq UI thoughts Andreas Bringedal
2003-11-20 10:37     ` keys and menus Brandon J. Van Every
2003-11-20 10:58     ` Xconq UI thoughts Bruno Boettcher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=OOEALCJCKEBJBIJHCNJDAEFKGMAB.vanevery@indiegamedesign.com \
    --to=vanevery@indiegamedesign.com \
    --cc=xconq7@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).