Midrange News for the IBM i Community


Posted by: Bob Cozzi
Rogue Programmer
Cozzi Productions, Inc.
Chicagoland
Eight simple ways to know if you have a bad IBM i Developer
has no ratings.
Published: 30 Aug 2015
Revised: 01 Sep 2015 - 815 days ago
Last viewed on: 24 Nov 2017 (1935 views) 

Using IBM i? Need to create Excel, CSV, HTML, JSON, PDF, SPOOL reports? Learn more about the fastest and least expensive tool for the job: SQL iQuery.

Eight simple ways to know if you have a bad IBM i Developer Published by: Bob Cozzi on 30 Aug 2015 view comments(3)

Here are 8 signs that your IBM i developer is a Pretentious Poser, uh, I mean: isn't as good as they might think they are.

  1. They still declare ad hoc fields.
  2. "SELECT *" is specified; not to mention the fixed-format SQL.
  3. Legacy Indicators #WTF?
  4. Using GOTO (anytime) instead of LEAVESR.
  5. Still using END instead of ENDIF/ENDDO.
  6. Uses SQLCOD (or SQLSTT) instead of SQLSTATE.
  7. Using cute but meaningless Screen IDs as if they're still writing WSU.
  8. Use of *INKx indicators; and even worse, using S/38 or S/36 standards #Duchebag

Return to midrangenews.com home page.
Sort Ascend | Descend

COMMENTS

(Sign in to Post a Comment)
Posted by: avrSteve
Premium member *
Comment on: Eight simple ways to know if you have a bad IBM i Developer
Posted: 2 years 2 months 27 days 4 hours 42 minutes ago

Thats a good starter list

Posted by: GFuste
Premium member *
Jacksonville, FL
Comment on: Eight simple ways to know if you have a bad IBM i Developer
Posted: 2 years 2 months 27 days 2 hours 39 minutes ago

They use /EJECT often and especially in between sub-routines.

Posted by: Ringer
Premium member *
Comment on: Eight simple ways to know if you have a bad IBM i Developer
Posted: 2 years 2 months 26 days 12 minutes ago

9. No comments 

10. Still coding in RPG III