• Subject: Re: Offload from the AS/400
  • From: HankHeath@xxxxxxx
  • Date: Wed, 5 Nov 1997 13:13:29 -0500 (EST)

In a message dated 97-11-05 12:48:01 EST, atostain@crecomp.com (Art Tostaine,
Jr.) wrote:

<< Guess what, the 400 is slow! >>

I've been dealing with this statement for years. It is an absolute falsehood.
Sorry, guys, but it is. The AS/400 is a damned fast machine.

The applications that I have seen written for it are some of the worst
garbage I've had to deal with, though. The competency of many of the RPG
programmers in creating a decent system has been missing. Why? Because most
of the programmers were "grown," not developed. [Hey, he's a decent operator.
Let's gie him a chance to write programs.]

IMHO, the main problem this platform has is the level of professionalism of
its developers. Be honest. Those of you in the systems arena (many of the
readers of this list): how often do you face a run-away application that
*could* run so much better if the programmers only knew what they were doing?

I realize that I'm not making any friends with this statement, but I am tired
of the blame going in the wrong direction. The only crew that writes worse
code IMHO is the VB crew. I do not propose certifying programmers. That
doesn't work. But I do propose that managers could do a much better job of
leading their programming staff.

Hank Heath
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].