Hey, I know a lot of COBOL developers and, on average, the last change the code they are working on happened just 20 years ago!
this post was submitted on 16 Dec 2024
0 points (50.0% liked)
Programming
17669 readers
161 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
Maybe “no one” can read it because “everyone “ posts YouTube links with some SEO bullshit shouting at me like a fucking tabloid, instead of a link to the readme of the video (transcript)? I know I’m old man shouts at void here but STFFFFFFFFU. Tldw.
Some people know it, and they make obscene salaries with their knowledge.
no, they don't
For non-video people like me: The World Depends on 60-Year-Old Code No One Knows Anymore
The real headline behind it: IBM plans to update COBOL via Watson AI to Java.
plans to update COBOL via Watson AI to Java.
it went from bad to worse
This is delicious. I hope they hurry up, and I hope they do it in a really large really public context.
I've had this conversation, but today's generation of AI won't:
"No, I can't just do a one for one translation. Some of the core operating principles of the language are different, and the original intent needs to be well understood to make the appropriate translation choice. If I just translate it one to one, with no understanding of the business context. you're going to suffer from years off debugging subtle but impactful bugs."
Get on with it IBM. Let's light this dumpster fire so we can all bask together in it's glow (and smell).
There may be a day coming in the next 100-1000 years when a learning algorithm is a suitable replacement for an expert engineer, but that day has not arrived (and the early evidence of that impending arrival hasn't arrived, either. I haven't seen evidence of AGI experiments with even toddler reasoning levels, so far. Toddler level reasoning wil come before AGI with infrastructure deployment skills, which itself is probably coming before AGI with expert business logic diagnostic skills. This could all be 20 years or 1000 years away. But we will probably see LLMs running deeply insightful life changing management workshops sometime roughly next week, since a trained parrot could do that. If we have an AGI that can meaningfully reason with small numbers in the next 20 years, we will be making great progress and on track for the rest to arrive - someday. If not, then we're probably waiting on a missing computational breakthrough.)
I always wonder if I should just learn COBOL and try to just do a few juicy contracts a year and focus on my other pursuits (farming and considering making a game, as well as vacation of course) the rest of the year.
Just knowing the language isn't enough to make the obscene money. You have to also be very familiar with the systems that use the language, and that takes years.
I wouldn't recommend it. I actually looked up COBOL jobs a while ago, and while they paid more, it was only like 20% more - not enough to make it worth it IMO.
My friend's mom gets called back for COBOL stints at major US banks all the time. I don't know how long it'll last, but apparently the list of people to select from and bring in is ridiculously short.
I don't know if this is realistic. Considering making a game is a full time job.
This isn't true. If you can get by while working part-time, you still have at least 40 hours every two weeks to work on your game.
It's one of my biggest regrets, that after school I immediately jumped into full-time job, even though I realistically could live comfortably with 1/3 of the pay I was getting, since young+no familly+no car+shared living reduces your living costs by a very large margin. My best friend did that and has been working only 2 days per week since. I was trying to keep up with him, working on our game in my free time, but it's simply not feasible to build on top of 40 hours per week of regular job, and then do anything meaningful on your side projects. I barely struggled to get myself to do at least 20h of work per month on the project, missing deadlines, and it sucked.
He, on the other hand, kept our game project afloat and moving forward, with 60+ hours per month, while also writing and running a large LARP for 100 of players, directing his own theater group, and in general successfully working on a lot of projects, including several smaller games.
The best advice I can give, if you want to be a game developer, is to 1) not work in gamedev and 2) work part-time. The IT salary should net you a comfortable life even on part-time pay, assuming it's not gamedev. Smaller studios will have difficulties keeping afloat if they need to pay you, and in larger AAA studio you will be the same code-monkey crunching JIRA tickets as you would be in any IT job, but for a lot less money. And the design freedom you get when your livelyhood doesn't depend on your art's success, be it games or anything else, is totally worth it.
For example, this game has been developed solely in free time, without anyone getting paid for working on it. It's not AAA and the development takes a long time, but it definitely doesn't need to be a fulltime job.
You probably dodged a bullet there, thinking you can "just make a game" with a polish that makes it playable. It is a skill you have to learn, several actually. You can learn that if you work in the gamedev industry so I don't understand why you recommend against it.
Taking x time off to make a game with low knowledge could be a fun endeavour but not more than hiking IMO.
Source: ancient gamedev
I forgot to add that I had a Masters in Game Development and Computer Graphics, which definitely helped, but I still learned most of my gamedev skills by regularly attending gamejams and working on my own projects. I've also started working in gamedev for the past year, and I wouldn't say that it teaches you much, since you are missing out on 80% of actuall development and only crunch JIRA tickets and bugfixes, as a junior that is, without being exposed to the more important parts or other skills. Assuming you join a larger studio with game in progress, in an indie studio with team of 10 people, you'll probably have a lot more responsibilities and impact on other stages of the game's development.
Yes, a small dev team is the ticket, and even then you might be excluded from marketing and all that jazz like funding, getting edited etc.
You seems to be on track to be a game dev of sorts, and who knows, maybe you'll make your own games one day, good luck!
Forgive a question from an oldtimer, what exactly is a master in game dev and computer graphics?
Do you learn how to code and like draw, model, rig & animate? Code 3D engine stuff? Game mechanics I guess? For 5 years?
I'm curious :-)
It was only two years, and it was basically half nornal computer science classes, and half working with engines, making a game with classmates and mentors from the industry throughout the year, and learning about rendering, AI behaviors (the videogame kind, not LLMs). The graphics part was about shaders, lighting, post-processing, global illumination, renderers and math, not modeling. It was mostly technical, but we had some game desing classes.
Eevee's heteroglot entry for COBOL is interesting, coming from … practically anything else.
There's also someone doing AOC in ABAP (basically SAP COBOL) who posts over in the AOC subreddit. I've looked at them and ... mhm, I know some of these words!
I've fallen down the rabbithole. I'm reading a free course (from 2001ish) on Cobol.
COBOL is Maintainable
I now question everything. I mean, technically, basically anything is maintainable in that it's possible...
I mean, the fact that more than half-century-old COBOL continues to be maintained does speak to the fact that it is maintainable. That might also be part of what makes COBOL painful to the average developer: You're not only dealing with a language that first appeared in 1959, designed for machines that were very different than modern computers; you're also dealing with over a half century of legacy code, including all that means for Hyrum's law.
Unfortunately maintainable and pleasant to work with are rather distinct concepts.
how to obtain this 'last person that knows cobol' title with whatever language goes extinct next?
Probably no longer possible now that we have generative AI, a coder can now be archived alongside the codebase itself.
you could just learn cobol. it's not going anywhere, unfortunately
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.
Every attempt at dissuading me only makes the fun of the challenge more enticing.
None of this matters as I have no work experience--only hobby crafting.
My point is that there will always be people willing to try and the more you tell us "you don't want to" the more us not so privileged with work-experience continue dreaming with deeper allure
Oh, I'm not trying to talk you out of it, I'm just making sure that you see all sides of the scenario.
I looked at some of the Y2K patches, I don't strictly know cobol either , but it's not that hard to read.
You'd think that code lying around would be refined as they had limits on space and everything was so mature. It's still pretty trashy :)
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.
At Uni doing CompSci in the mid 1980s, we were told the likes of Cobol was dead, and we were taught Pascal :)
Cobol is dead.
And I think it's about time to start telling people Java and Perl are dead, so they can marvel at how much Cobol and Java and Perl are still doing in production after death.
Maintaining old code is the real drawback. Surely nobody finds that fun.
COBOL is just the turd on the shit cake.
Pay me to do it remotely and I'll jump at the chance
Friend of mine maintains COBOL for an insurance company. He lives on the opposite side of the country from his business, and is only on call one weekend a month.
Dude got hired before he even graduated, getting paid 70k, and gets to live wherever he wants.
I would kill for that lol
70k is likely way underpaid for dealing with COBOL. I've heard of people making 200k for being on-call