Re: [Fresco-devel] Re: ACE

On Mon, Nov 25, 2002 at 11:30:45AM -0700, M. Evans wrote:
> I'll spell it out. 
> ...
> 
> Oh, sorry, I thought IDLs were meant to hide internal dependencies.
> Guess not. :-)
> 
> So far all I've heard is that it's too hard to build, so you gave up
> and rolled your own code.  Seems to me it would make more sense to
> contribute to the ACE project.
> ...
> 
> Oh come on.  I'm a professional making six figures.  I know my code
> and how to manage my time.  I've seen the not-invented-here syndrome
> before.
> ...
>
> Besides, I think the whole overkill notion belies a failure on your
> part

Ok, look. Perhaps you're just a troll, and i shouldn't be writing
this.

But, on the off chance you're not, i have one question to ask you:

How long have you been tracking Fresco development?

Personally, i'm a computer professional. I deal with design issues all
the time. I've been subscribed to fresco-devel and its predecessor for
over a year now.

I don't contribute much.

But, if and when i do contribute, it will *not* be:
- change your licensing scheme because i know better
- throw out this code and merge with this marginally related project
because that's the way i think it should have been done way back when
the decision was made by people who knew what was going on
- i can't believe the project's come this far with the decisions that
have been made. you should all step back and let me take over, because
i have experience.

If you disagree with a decision, don't read the first link you find on
the topic and post it. My CTO does that, and i end up having to read
random documents on data warehousing for OS/390 (we run Linux).

Instead, ask for access to the mailing list archives, and a pointer to
where it was discussed before. Look at the issue tracker, where much
of the technical discussion takes place. Maybe even the IRC
logs. Then, if you still disagree, try and bring it up in *that*
context -- relevant to the project.

If you look into a project and find it's not structured or run the way
you would have structured and run it, well, hey, that might be because
you're not running it. It might be a project different from any you've
worked on. It might be a different methodology that the core
developers are more familiar with.

If you want to be taken seriously in a discussion, spend time watching
the project. Get familiar with the way things work. Don't show up and
expect everyone to bow to your experience. There are many experienced
people here.

-johnnnnnnnnn