Former COBOL programmer here with about 5 years of experience. I got out of IT in 2012, staring at a green screen all day and having limited human interaction just wasn't for me.
C++ still huge in embedded, mostly what Emerson and John Deere use. Amazon contacts me a few times a year trying to get me to take a C++ position.COBOL and Mrs Tomlinson who taught it at ISU made me hate that coding language so much I probably would rather work at McDonald's than code that for a living. Just my opinion obviously but had to take COBOL as part of my MIS classes and was by far the least favorite of the programing languages we had to take. C++ and Visual C++ were 2 others we had to take and Visual Basic was an elective. All are pretty much obsolete languages now but probably some niche jobs out there to support existing systems coded with them.
John Deere has options to split work with someone for C++ so both people could do 20hr a week but currently in hiring freeze and not sure how long it will last.Seems like there is realistic possibility that my wife could make $500k/yr and I can start up golf as a hobby….? J/k
I appreciate everyone’s response and please keep them coming.
Im sure she has stories about Fred Choobineh too. That guy was a legend. Every college of business student had to take his course whether you were a MIS major or not. I just wish I could have taken his course as a 21 year old instead of a 19 year old freshman as I hear he had some fun FACs on WelchI just shared this with her, she liked him. Didn’t care for her due to her style…
You either love it or hate it, I could code til I dieI always thought I'd like to learn to code, and then I had to debug one. No thanks.
Had a COBOL assignment that I had to take an input file through code and generate an output file with the results. It compiled without errors but when I ran it my PC locked up and after pulling the power cord to reboot found an output file that was several gig in size and it should have been less than 1 MB. Took it to my TA who couldn't find where my loop was either so I basically had to comment out the part of code that generated the output file when I turned in the assignment. Still got a passing grade as 50% was just having code that compiled and the logic looked right but it would not stop writing to the output file for some reason.I always thought I'd like to learn to code, and then I had to debug one. No thanks.
C++ opens up virtually any industry she’d be interested in.I would love/appreciate to hear your thoughts on the topic/suggestions.
We are not that far along yet, merely exploring if COBAL was an option. She knows C++ and Visual and I remember her being bored/frustrated with COBOL before she left the workforce.
Our kids are close to all being in school and we are looking at her filling some anticipated free time, but not available for a typical 40 hr/wk corporate career.
Thank you, Cyclone Nation!
Funny…I always thought I’d like to do finish carpentry, and then I tried to cope an inside corner.I always thought I'd like to learn to code, and then I had to debug one. No thanks.
I'd have her look at large financial/insurance companies that have been around awhile.
@cyphoon might also have some thoughts
Funny…I always thought I’d like to do finish carpentry, and then I tried to cope an inside corner.
Converting is a long expensive process and the mainframe is your best bang for the buck. Servers are great for single object operations but they were never designed to handle large chunks of data. According to Broadcom technologies, about 72% of all computing is done on mainframes at about 8% of the cost. Item 3COBOL is still needed in plenty of places. Our company has a mainframe system that uses both assemble and cobol. And while that's antiquated stuff, it works really well because the code has been around for 40 years.
Why would we still use those old systems? Because when systems have been around for 40 years they have had a ton of code optimizations, bug fixes, and business logic added in there. And there is lots of sprinkled in dead code and other technical debt. This makes it very time consuming to convert off of. Especially for systems that do financial work and the importance of getting money right. Most companies have a hard time stomaching the cost/effort/time of converting.