Good points. A lot of us started off in operations first then went on to application development. Eventually, some of us moved over to systems programming. Then.later the silos were created for operating systems maintenance, networking, and database. Today circling back, all those roles were melded into one individual wearing many hats, thanks to the Muckety mucks trying to kill the mainframe. So here we are. Bill Janulin. Sent from Yahoo Mail on Android On Mon, Feb 6, 2023 at 13:37, Paul Gorlinsky<p...@atsmigrations.com> wrote: Absolutely! They should be taught how to program and debug first, then the constructs of individual languages.
Many of us have programed on all sorts of machines from the IBM mainframe, to the IBM PC, 8080s, z80s, Univac 1050-II, Xeon, Arm, etc. and different languages from all the of different assemblers, PL/I, COBOL, FORTRAN, BASIC, REXX, C, JAVA, et.al. And can move freely between them. But alas, even company trained systems programmers AREN'T systems programmers... They are installers, administrators, etc. that can't write a lick of assembler code ... ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
