Subject | Re: [IBDI] Use the source, Luke! |
---|---|
Author | Paul Beach |
Post date | 2000-06-23T12:53:19Z |
Doug,
an R&D Engineer, more like a C hacker (and I use hacker more in its
dictionary sense - rather than the technology usage), the code will
certainly help, but its not going to be the complete answer.... I have found
running the code in debug was more helpful, especially in certain areas, but
even this isn't the perfect answer. We (InterBase) recognise that we have to
document the code, and how it works, and how it all interacts. Work has
already started on this, and you will see information re. the code and what
it does, added as fast as we can realistically do it.
The more people who come to understand the code and what it does, the better
it will be for all of us (InterBase included).
Regards
Paul Beach
Vice President Sales & Marketing
InterBase Software Corporation
Tel (USA):+1 831 431 1097
Tel (UK):+44 (0) 1844 354465
Mobile: +44 (0) 7887 890375
E-mail: pabeach@...
> This is a comment on open source process as it relates to our currentviability
> situation and a reflection on what I have seen recently in online venues.
>
> I really wonder how many developers are going to actually take the time to
> research the source code thoroughly enough to be able to use it to answer
> their questions. Or to validate ideas and suggestions for improvements. Or
> to make changes themselves.
>
> Several recent messages have started out along the lines of "This is an
> idea which my be lame but until I have the source available I cannot check
> out it's viability..." My question is, do people really think the
> availability of the source code is going to help them discern the
> of a product suggestion? Are they really prepared to do the intense worktake?
> necessary to research the source code? How long do they think that will
>Speaking as someone who is familiar with the source code, but certainly not
> I look forward to reviewing the source code for the sheer pleasure of it.
> (Mostly because I never thought I'd ever see such a thing.) However, I
> don't expect to understand it well enough in any reasonable time frame to
> be able to have it answer questions I have, let alone for me to offer
> suggested changes. Unless it is documented in some magical way which is
> orders of magnitude clearer than any other source I've looked at, it will
> take a long to time learn!
>
> (Sorry, folks, I just had to share that dose of reality.)
an R&D Engineer, more like a C hacker (and I use hacker more in its
dictionary sense - rather than the technology usage), the code will
certainly help, but its not going to be the complete answer.... I have found
running the code in debug was more helpful, especially in certain areas, but
even this isn't the perfect answer. We (InterBase) recognise that we have to
document the code, and how it works, and how it all interacts. Work has
already started on this, and you will see information re. the code and what
it does, added as fast as we can realistically do it.
The more people who come to understand the code and what it does, the better
it will be for all of us (InterBase included).
Regards
Paul Beach
Vice President Sales & Marketing
InterBase Software Corporation
Tel (USA):+1 831 431 1097
Tel (UK):+44 (0) 1844 354465
Mobile: +44 (0) 7887 890375
E-mail: pabeach@...
>
>
>
> ------------------------------------------------------------------------
> IT Professionals: Match your unique skills with the best IT projects at
> http://click.egroups.com/1/3381/5/_/679568/_/961762712/
> ------------------------------------------------------------------------
>
> Community email addresses:
> Post message: IBDI@onelist.com
> Subscribe: IBDI-subscribe@onelist.com
> Unsubscribe: IBDI-unsubscribe@onelist.com
> List owner: IBDI-owner@onelist.com
>
> Shortcut URL to this page:
> http://www.onelist.com/community/IBDI
>
>