> IT professionals should work in a mainframe environment at some point (2015) ... in order to experience and learn that: * Max depth of your file system tree

> IT professionals should work in a mainframe environment at some point (2015) ... in order to experience and learn that: * Max depth of your file system tree is 2 * Password must be changed every month * Max password length is 8 * Alphanumeric chars only * No upper/lower case distinction * There's nothing wrong about using java 1.7 in 2019 * "if <customer == XYZ> then <feature>" is just fine as a code pattern. * To release uncompiled & untested code is OK. * To release code with compilation errors is OK, too. * To use CVS could be a huge step forward. Because the thing you've been using can manage only code files but not configuration files. Albeit "manage" is a huuuge overstatement here. * Print out the list of changes and stamp it with a rubber stamp is the way to fix it. * Permanently. * Permanently-Partially. Half of the team was printing the other half was copy-pasting the list of changes to a file. * For years. On the PCs. Not on the mainframe. * In MS Word documents, not as a plain-text. Because reasons. * Ok, several months after my predecessor left I gained enough confidence to ask for the permission to abandon the printing in favor of the MS Word. I was injured at the time and I thought like the pitiful picture of me limping between the printer and the desk 4 times a day could help me in an argumentation. * There are mainframe developers who don't even know how e.g. XML looks like. No kidding. * And they won't get fired neither asked to learn anything new. And their salary has 6 digits. * etc.