RE: WDSC and Linux

>So you're not a programmer, you're an application assembler.  You're right,
we are from different worlds.

Joe, you are a bit twiddler at heart.  I am a programmer.  Like the
discussion we had before, I am _not_ a case tools developer.  I enjoy a rich
set of API's to get my job done.

<snip>
God forbid you should have to learn a low-level concept or even develop a an
ENTIRE SOLUTION!  Obviously it's not important to actually understand what
the computer is doing, as long as you can get pre-fabbed pieces that you can
slap together to get your job done.
</snip>

Joe, just because you know that 1=on and 0=off doesn't mean crap if you
can't put them together to make a good application in a timely fashion.  I
get so sick of you saying that half of us here aren't programmers just
because we don't have time to read through MI manuals.  I respect your
knowledge and use it when I can filter out your personality.
<Tongue-In-Cheek>Maybe everything you say is right and every person you have
argued with is wrong... I guess I haven't considered that.</Tongue-In-Cheek>


<snip>
Certainly you wouldn't want to take the time to have an overall corporate
mission statement, then use that to design a flexible architecture that will
allow you to meet current and future requirements on a timely basis.
</snip>

Sometimes I think you exist to be a thorn in my side to every comment I
make:-)

Impossible(at least where I work).  We have been working on a project for
two plus years trying to get standards defined for 5 different IT depts.
within our corporation, and we are still trying to do it.  It basically came
down to us agreeing on standards that we have yet to create, and that would
be XML.


I am done with this discussion,
Aaron Bartell



-----Original Message-----
From: Joe Pluta [mailto:joepluta@xxxxxxxxxxxxxxxxx]
Sent: Thursday, July 24, 2003 12:11 PM
To: CODE/400 Discussion & Support
Subject: RE: WDSC and Linux


> From: Bartell, Aaron L.
>
> The problem is that we are
> trying to do it with tools that make us first learn low-level concepts (or
> even develop entire solutions), and then try and get the project
> out within the deadlines provided.

God forbid you should have to learn a low-level concept or even develop a an
ENTIRE SOLUTION!  Obviously it's not important to actually understand what
the computer is doing, as long as you can get pre-fabbed pieces that you can
slap together to get your job done.

Certainly you wouldn't want to take the time to have an overall corporate
mission statement, then use that to design a flexible architecture that will
allow you to meet current and future requirements on a timely basis.

So you're not a programmer, you're an application assembler.  You're right,
we are from different worlds.

Joe

_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.

NOTE: WDSc for iSeries disucssion has it's own mailing list.
Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsc-l