Thanks; agreed. And I did say, "Understand application and system design, architecture, testing and usage. Contrary to the old joke, users don't exist to test system programmers' system programs. Systems exist to perform useful work, so understanding the implementation food chain helps get your job done."
I've known too many systems people who disparaged applications developers and applications -- that's silly, hostile, and career-limiting. And it's backwards in relative importance of applications/systems to organizations! The article's orientation was somewhat shaped by my perception of the Destination z website being more for systems people than applications developers and my own (mostly) systems background. So I'll save the idea of application developer resolutions for another article, maybe a year from now. While -- as you note -- many tips apply to both areas, each has unique aspects. So I'll expect you to suggest application development tips! "Farley, Peter x23353" wrote: Not a bad article Gabe, but I'd like to point out that the maxims and advice you list are applicable just as much to Application programmers as to System programmers. We, too, need to be open to new technologies as well as constantly updating and sharing our current skills and knowledge base. And documenting what we do is just as important as the Systems gurus documenting their work, and for the same reasons. Etc., etc. -- Gabriel Goldberg, Computers and Publishing, Inc. [email protected] 3401 Silver Maple Place, Falls Church, VA 22042 (703) 204-0433 LinkedIn: http://www.linkedin.com/in/gabegold Twitter: GabeG0 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
