Don't forget the 360 assembly language. In the 2000s I know someone who made enough money to retire in Hawaii because he wrote printer drivers for the z-Architecture that scaled better than the print drivers from IBM in assembly language.
If you look at COBOL jobs you see a lot of them require you know 360 assembler because even after all these years it is common for z-Architecture apps to have some subroutines written in assembler which is a serious porting problem since you could otherwise switch to GNU COBOL on Linux or do a COBOL-to-Java translation or something.
Reminds me of the bad old days when it was normal to write inline assembler in Turbo Pascal, a decade ago I did work on some C++ code that used assembly for SIMD instructions though but if we were doing the same thing today we'd use Torch or Tensorflow or something.
Don't forget the 360 assembly language. In the 2000s I know someone who made enough money to retire in Hawaii because he wrote printer drivers for the z-Architecture that scaled better than the print drivers from IBM in assembly language.
If you look at COBOL jobs you see a lot of them require you know 360 assembler because even after all these years it is common for z-Architecture apps to have some subroutines written in assembler which is a serious porting problem since you could otherwise switch to GNU COBOL on Linux or do a COBOL-to-Java translation or something.
Reminds me of the bad old days when it was normal to write inline assembler in Turbo Pascal, a decade ago I did work on some C++ code that used assembly for SIMD instructions though but if we were doing the same thing today we'd use Torch or Tensorflow or something.
https://archive.ph/Uw7TM
Rubbish skills in Cobol =/= a rubbish IT system
Disappointingly narrow focus for such a poignant title.