|
I would venture to suggest there are no "killer" features in CODE (or any IDE Editor) over SEU. Rather, we have a greater range of complementary tools which we can employ as appropriate - use whichever is best for the job in hand. SEU might be the tool of choice for making quick and simple changes ("fixes"). CODE might be more applicable for major enhancements or new development. Personally, I find BOTH tools to be very productive in this Brave New World of "flexible working" - i.e. working remotely from the iSeries. Client tools such as CODE allow me to download source to a PC and work completely detached from the iSeries. (I could do the same using FTP and Wordpad - but CODE gives me the syntax checking, Help, verification, etc to ensure the finished article is as clean as possible.) But then, when I am fixing minor errors, I find it quicker to use SEU than CODE - because of the communication download/upload overheads. I imagine if you are a freelance worker, (contractor, consultant, etc.) you will find the client-tools such as CODE/WDSc to be of benefit. If you work in a regular office environment you may not see the benefits so readily. At the end of the day - despite all of the hype and fervour - I suggest it's a question of choice and personal preference. Whatever works best for you. Final thought: Keep an open mind and be willing to learn - that next job/contract might just depend on your new-found skills. Brian Parkins
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.