Exactly. For a long time one of those companies were clearly going for the status quo: everything is going fine, no issues here.
Then all of a sudden they noticed that soon all of their Cobol-devs would be on retirement, so they started the training stuff, like a way to buy some time and push forward the conversion they'd be facing.
Exactly. For a long time one of those companies were clearly going for the status quo: everything is going fine, no issues here.
Then all of a sudden they noticed that soon all of their Cobol-devs would be on retirement, so they started the training stuff, like a way to buy some time and push forward the conversion they'd be facing.
But now they don't have that conversion yet, and not really skilled Cobol-devs soon. So they'll start to plan for that overdue conversion, and I'm sure they'll be taking some shortcuts there, which will result in lesser quality code. (and then they can blame that new 'immature' technolgy ;-) )
Exactly. For a long time one of those companies were clearly going for the status quo: everything is going fine, no issues here.
Then all of a sudden they noticed that soon all of their Cobol-devs would be on retirement, so they started the training stuff, like a way to buy some time and push forward the conversion they'd be facing.
But now they don't have that conversion yet, and not really skilled Cobol-devs soon. So they'll start to plan for that overdue conversion, and I'm sure they'll be taking some shortcuts there, which will result in lesser quality code. (and then they can blame that new 'immature' technolgy ;-) )