Auf YouTube findest du die angesagtesten Videos und Tracks. Außerdem kannst du eigene Inhalte hochladen und mit Freunden oder gleich der ganzen Welt teilen.
You could most likely find some damn spicy contracts. The real question is, is it worth it?
You’re going to retrofit some old code to fix an upcoming date bug, or try to make some changes wrapped around security vulnerabilities. But these systems we’re relying on, they’re in banks, air traffic control, and in hospitals, we’re not just depending on these boxes but critically depending on these boxes. There’s almost nobody sitting around to give you a second set of eyes on the code, probably almost nobody capable of doing proper QA on the systems you’re working on.
I’d bet you will probably work for experience or exposure and very little money on the first job or two you take, since you don’t have any hands on experience. But after that it’s kind of a name your own price gig.
good cobol programmers are probably the highest paid programmers there are. mostly because there are so few of them and the systems are so critical.
but like… it’s not going to be fun. cobol as a language is extremely verbose, and you’re not going to actually develop anything. it’s just fixing compatibility problems and y2k issues all day.
you could just learn cobol. it’s not going anywhere, unfortunately
As someone who has worked with it, it’s not too bad. Lots of $$ if you know someone.
The biggest issue (that she goes into), is the lack of context. Why is the thing doing what it is doing is the hardest part
Like could I learn it enough to obtain a real job tho? That pays real money I mean?
You could most likely find some damn spicy contracts. The real question is, is it worth it?
You’re going to retrofit some old code to fix an upcoming date bug, or try to make some changes wrapped around security vulnerabilities. But these systems we’re relying on, they’re in banks, air traffic control, and in hospitals, we’re not just depending on these boxes but critically depending on these boxes. There’s almost nobody sitting around to give you a second set of eyes on the code, probably almost nobody capable of doing proper QA on the systems you’re working on.
I’d bet you will probably work for experience or exposure and very little money on the first job or two you take, since you don’t have any hands on experience. But after that it’s kind of a name your own price gig.
I know you’re joking, but it’s one of the only kinds of jobs I can picture motivational enough to pursue
good cobol programmers are probably the highest paid programmers there are. mostly because there are so few of them and the systems are so critical.
but like… it’s not going to be fun. cobol as a language is extremely verbose, and you’re not going to actually develop anything. it’s just fixing compatibility problems and y2k issues all day.