31 ms·
Banks scramble to fix old systems as IT 'cowboys' ride into sunset
- polm23 10y agoI remember running into someone who worked at an insurance company in my home state and mentioned their whole system ran on COBOL. I asked her how she hired programmers and she explained they hired recent college grads with no technical background and trained them from scratch, since it was easier and cheaper than hiring experienced COBOL programmers. Looking back I'm surprised they had the institutional knowledge to maintain systems that way...
- StillBored 10y agoThey don't. That is why they need to call back the guys that retired. Any of the new hires with talent quickly discover they can double their salary by doing pretty much anything else in IT and move on. IBM and their customers want to turn the whole thing into a McDonalds style business, but the burgers keep burning and they keep having to call people to come in and rewire the microwave and unplug the toilet.
- watwut 10y ago> Any of the new hires with talent quickly discover they can double their salary by doing pretty much anything else in IT and move on. Not necessary. They do not know current frameworks and tools and probably don't know the knowledge is transferable. Effectively, they need to find a company willing to train them and the one that hires by aptitude on whiteboard test only.
- user5994461 10y agoYes. Very likely that they can't get a better job. As the previous comment said, they are trained from scratch having no experience in tech whatsoever and mainframe is not remarketable to a web company.
- eru 10y agoGoogle is willing to hire anybody who can solve a few basic algorithmic problems.
- user5994461 10y agoThe hardest part of Google is to be accepted for an interview, which they won't. The second hardest is to actually answer the questions in the interview, at that they don't stand a chance. Don't overestimate a guy who is doing a job reorientation from a random degree, having barely touched a computer before. Last but not least, Google is only in a handful of locations in the World, banks are more common.
- eru 10y agoThe trick to get your interview at Google is to get somebody to refer you. (And that's not that hard. If you can't find a Googler in person at a meetup, hang out online and write to a few random Googlers. They get a hiring bonus, so if you provide them with the information they need (it's a small questionnaire about you they have to answer plus your CV), lots of them are happy to refer you.) The interview is a bit peculiar, and not all that correlated to what even Googlers do on their day job, but it's trainable, and you can repeat every year. Do Facebook at the same cadence, but six month out of phase, and you got a steady stream of interviews. Add eg Microsoft and some other companies, and you are virtually guaranteed to land a decent job at some time. And that holds even after I agree with your caution about overestimating a random but intelligent person. It is quite the time commitment, though. The locations weren't too much of a problem for me. But I do have to admit that when I joined my preferred location of Singapore didn't really have any engineers, so I settled for Sydney. And as your comment suggests, yes, I was working for a bank in Singapore before.
- user5994461 10y agoYes, it's good advice, I know how this works. Meetups and linkedin messages. You still need to be in a google location to come across a meetup (there are only so few offices in the world) and your profile might need to be better than "I dropped from art school last month. I like computers."
- nodesocket 10y agoCobol expert = $1,000 an hour rate. Great niche, but eventually will get replaced. Awesome marketing and PR for his company Cobol Cowboys (http://cobolcowboys.com http://cobolcowboys.com. > His wife Eileen came up with the name in a reference to "Space Cowboys," a 2000 movie about a group of retired Air Force pilots called in for a trouble-shooting mission in space. The company's slogan? "Not our first rodeo."
- lithos 10y agoThey still teach COBOL and RPG at my old tech school. Went through the class and the tech behind the old mainframes are actually pretty neat. multi CPU processing, dynamically choosing which resources to use, easily transferring work to other machines and how everything works together so tightly. Just a lot of concepts that are getting 'rediscovered' instead of just looking at systems older than me (properly the same feelings that the people who learn lisp go through). They also put us through the normal java/visual basic hazing as well. Though I ended up in electrical engineering.
- frozenport 10y agoA few concepts such as having redundant CPUs introduced a lot of technical challenges without clear pay outs. The previous inspiration was the comparably high cost of computing equipment. Redundancy techniques such as those inspired by the block chain, seem to be much hipper now days.
- theandrewbailey 10y agoWhen I peeked into mainframe development in college, it seemed like a lot of those technically heavy features were implemented because some manager said so, and someone else was willing to pay for it, no matter the practicality (or cost).
- hackerboos 10y agoWe have 50,000 lines of RPG code we need to replace over the next decade. Since the last RPG dev at our company is over 65 years old and can retire at any moment. It's going to be funny when we replace it with Java and our business guys ask why it runs much slower.
- deleted 10y ago[deleted]
- creaghpatr 10y agoIt's easy to forget that most businesses America aren't publicly traded companies. This guy found a profitable niche, realizes that it isn't sustainable long term, but makes perfect sense for him and his peers. Good for him.
- ams6110 10y agoThe problem really isn't COBOL. COBOL is not a difficult language. It reads almost like English sentences. Any competent programmer would not be challenged by COBOL. The problem is all the glue. JCL, SNA, CICS, ISM, ISPF, etc. It's like the difference between Java (the language) and J2EE, except in the context of 1970s computer technology. It's not intuitive and not something you can really work through without a lot of training and experience.
- jwilliams 10y agoIndeed - and although COBOL is the topic here, the issues are pretty similar with J2EE. There are a lot of legacy J2EE applications in banking and finance. Let alone the skills and inside knowledge you need to know the various containers and modern(ish) glue (WebSphere is the prime example). Underlying this is that banks used to see IT/Technology as competitive advantage. A lot of tech came directly out of the banks. IT became a cost-center in the 90s and it was never the same. The irony is that this tech stack was pretty good and fit-for-purpose for a lot of banking workloads. Plus it kept working... so that just lessened the investment required.
- clumsysmurf 10y agoAt my last employer, there were a few "mainframers" (we called them). I was curious so I would ask my mainframer coworker how things worked on his end. I always struggled to understand, because it seemed everything was different ... the terminology, the culture, the ideas. I couldn't use analogy to tie what he was describing back to what I knew.
- tyingq 10y agoMakes sense, as there's little in common for many base concepts. You deal mostly in stream files, they probably deal mostly in record oriented files..where their "kernel" understands it's record oriented. Your terminal emulator sends every keystroke the the host. Theirs doesn't send anything until they specifically make it do so. You have ASCII or utf8, they have EBCDIC. Some of it is crossing over though. They used to talk about virtual machines before they were common for us. The concept was confusing at the time.
- catmanjan 10y agoFrom the article "Experienced COBOL programmers can earn more than $100 an hour" In Australia that's a lot, but my understanding is that it's common for American developers to be on way more than this...
- bluedino 10y agoYou can charge that much to hack on Wordpress in the US
- ZoF 10y agoThis is simply untrue unless you're lying as a freelancer or working with a big enough wordpress installation that 'hacking on wordpress' would hardly be the correct description. (read: most hosting companies effectively 'hack on wordpress' for you for free from most companies as a 'support option') Also fyi, you can generally charge "that much"(as much as the US) elsewhere assuming you're proficient in english.
- cdsx 10y agoI'm curious what your experience in Australia has been for you to think that. In my experience that's not what I'd call a lot in Australia, most commonly your average basic IT contactor will charge $80-120/hr, let alone any sort of speciality.
- bananaboy 10y agoWhat's a basic IT contractor? $100 seems to start getting to the upper end of what I'd call a basic IT contractor. > $100 seems to be for more management/architect type roles according to http://au.hudson.com/portals/au/documents/salary%20guides/2017/HudsonSalaryGuide_TechnologyDigital_AU.pdf http://au.hudson.com/portals/au/documents/salary%20guides/20... and http://www.greythorn.com.au/media/greythorn/greythorn%20market%20insights%20and%20salary%20guide%202014_2015%20australia%20pay%20rate.pdf http://www.greythorn.com.au/media/greythorn/greythorn%20mark....
- 10y ago
- janwillemb 10y ago> One COBOL programmer, now in his 60s, said his bank laid him off in mid-2012 as it turned to younger, less expensive employees trained in new languages. [...] "The call back to the bank was something of a personal vindication for me," he said. I find this being an oddly satisfying part of the story
- kingnothing 10y ago"Experienced COBOL programmers can earn more than $100 an hour when they get called in to patch up glitches, rewrite coding manuals or make new systems work with old." Any contract-based engineer would charge that, or more, regardless of the language. Fortune 500 companies are happy to pay $300 / hour to a consulting company for engineering time.
- randlet 10y agoYeah, $100 an hour for contract COBOL expertise sounds very low, but maybe I underestimate the number of COBOL people still around.
- Spooky23 10y agoA lot of COBOL stuff is cut and paste crap, or just updating basic fields. There are people paying as little as $35/hr for these types of people, although most of the people at that rate are barely qualified to turn the computer on.
- pmiller2 10y agoTo be perfectly fair, turning on a mainframe or minicomputer is a nontrivial operation.
- meddlepal 10y agoAny particular reason why?
- samat 10y agoNOT QUALIFIED
- pmiller2 10y agoIt's a multi-step process, and every system is different. It's not just a matter of flip the switch and wait for it to come up. If you're looking at something really primitive, you might even literally have to toggle in a boot loader program. These 2 Youtube videos show how to initialize an S/390. The top comment on the second video is really good, too. https://www.youtube.com/watch?v=ytMgyrZm87A https://www.youtube.com/watch?v=ytMgyrZm87A https://www.youtube.com/watch?v=qrKbh5HwF3Q https://www.youtube.com/watch?v=qrKbh5HwF3Q
- dsr_ 10y agoThe problem is technical debt. Banks didn't realize they were software houses, they thought that IT was a tool.
- hackits 10y agoTechnically IT is a tool its their to service the business requirements.
- dsr_ 10y agoThat used to be true - up until sometime in the late 1970s/early 80s. Since then, banks are IT. Take that away and what's left?
- tmnvix 10y agoA banking licence (otherwise known as a licence to print money).
- lmkg 10y agoMade me think of the following Doctorow quote: There are no airplanes, only computers that fly. There are no cars, only computers we sit in. There are no hearing aids, only computers we put in our ears. There are no 3D printers, only computers that drive peripherals. There are no radios, only computers with fast ADCs and DACs and phased-array antennas. http://craphound.com/news/2011/12/27/the-coming-war-on-general-purpose-computation/ http://craphound.com/news/2011/12/27/the-coming-war-on-gener... It's perhaps natural this extends from the computers to the companies that make them: There are no banks, only financial IT companies. There are no TV broadcasters, only media IT companies. Et cetera.
- flukus 10y agoIt is amazing how many companies don't think they're software companies, even though they are 100% reliant on their in house software. "We aren't a software company" is even a direct excuse I've heard a few times to justify ignoring technical debt.
- mbloom1915 10y agoIt's certainly not just banks, very much utilities too. putting off investments in core IT capabilities has become the norm and when you've dug a hole this deep, might as well keep on digging!!
- coleca 10y agoThat's why I'm keeping my COBOL for Dummies and MVS/JCL handbooks as my retirement plan should the markets go south on my 401k. :-)
- nickbauman 10y agoI've worked in the financial sector as recently as 2006. Without getting too specific, some of the financial systems I worked on underpin large sectors of the economy, across many banking chains. While Java was starting to take over these systems, thankfully the banks and regulators were hedging their bets on JEE with the knowledge that someone would eventually have to take over these systems. They were starting to think about growing an intergenerational community and started hosting applications in smaller chunks that individually comprised less risk (long before microservices was a coined term) and thinking in terms of APIS not implementations. They're not idiots. Having said that it might be good to ask your local bank how much of their systems are implemented in COBOL.
- parthdesai 10y agoAnecdotal, but my friend knew VP of Information Technology at one of the big 4 banks in Canada really well. The VP told my friend to learn COBOL and if he passed the interview, they give you a blank paper where you write down your salary.
- nickbauman 10y agoWhat this VP should have been doing was figuring out how to get out of that scenario entirely.
- parthdesai 10y agoWell VP could have been exaggerating a bit as well since we were uni students back then and my friend was doing his internship there. He knew the VP through robotics.
- gpderetta 10y agoNote that, in a bank, VP is not a particularly important position. A senior software developer anywhere else might have the VP title in a bank. It is very possible that your firend's friend wasn't involved in any hiring decision at all and it was just internal hearsay. Source: I'm VP at a large bank.
- exabrial 10y ago15 years of bad executive decisions adds up to a problem? Oh man. Say it ain't so.
- contingencies 10y agoFirst employee/architect of Kraken here. (Now does >USD$10M+/day of volume by my estimate) Accounting systems of all kinds should be generic and open source. Why do we need banks at all? It's not like this infrastructure really has any special characteristics. Most of it even has downtime and batch jobs. Fact: The bulk of banking is just recording some numbers at a stupendously simplistic resolution, with maybe 64 characters of description and a date. A few weeks ago I spent a day interviewing 20 different Hong Kong banks about API availability for cross-border RMB transactions. None at all offered it. We're reaching a point where the financial systems of a mid-level company exceed those of the banks they are forced to utilize. Modern requirements include things like: 24x7x365 availability, multilingual, arbitrary asset type support (energy, carbon credits, cryptocurrencies, space, time, etc.), multi-asset type accounts, new settlement networks, real time reporting and AML/KYC, all features API-available, new and established customer interaction through non-snailmail/physical means, customers routinely in different countries, multi-user accounts with disparate access levels (eg. accountant/auditor/spouse/kid), multiple legal jurisdictions with clashing regulatory frameworks, settled-means-settled, regulator-forced free market integration for non-core (ie. account-related) financial services such as loans/forex, redundant service provider availability for every function, meaningful SLAs/reputation for service providers, routing and/or provider selection based upon nontraditional metrics such as ethical investment rationales, etc. The same set of requirements goes up and down the supply-chain: people want to reason with their suppliers and customers about stock, settlement status, payment and contracts, they sometimes need backups in case of failure down the chain, and they care about reputation. Frankly the whole area is such a mess I am expecting an open source core accounting project to take over the sector. Probably it will begin in smaller/developing world banks and move toward the big guys like a meteor. For some evolving thoughts on the area (from 2012, but literally picked up again in the last 2 days) see http://www.ifex-project.org/our-proposals/ifex http://www.ifex-project.org/our-proposals/ifex
- mamcx 10y agoThis sound good, but already exist tons of open source solutions in this space and nothing look good enough. I wish to build some of this, but how will pay for it? --- BTW, http://plaintextaccounting.org http://plaintextaccounting.org have some good ideas about this. I think this is the way to go, but how make it work with a database instead
- bertlequant 10y ago"Come check out our data center". Tape robots. Compliance's friends.
- sanguy 10y agoBeen working on accounting systems in RPG and COBOL since ~1992. I also know C/X86ASM/Pascal/Delphi/VB/Fortran. Never bothered with C++ that much; played with Java a bit but Oracle irritates my bowels so moved away from that. As mentioned in the article it's good work; but it is also not easy work. You tend to go through cycles of being pushed out to brought back under extreme emergency at any costs to get stuff working. Only for the cycle to repeat. Companies never think of the old guys as the ones to implement the new system - that's a job for the "enterprise experts" - I can't even keep track of how many "rewrites" I've seen in my life fail because of this. We are the dinosaur club; but it's a club that pays extremely well (high 6 figures a year without working too hard if you are talented and have a good client base and reputation), but like fossil fuel one day it will all be gone ;)
- movedx 10y agoI smiled at your last comment. You're clearly a charming individual :-) Out of interest, what's the solution here? With your experiences in mind, what are the banks doing wrong from a technological perspective? I get the impression banks should almost start again on the side, building a completely new bank they then (manually?) move customers over to, or just use to take in new customers whilst waiting for the previous ones to die out. I guess if they built a whole new system, wouldn't it then be a "simple" case of doing a money transfer into the new system?
- UweSchmidt 10y agoYou can't wait for customers to "die out" as their mortgages will go on for decades. You definitely need a customer's old data in the new system. Now you have to maintain and develop two systems - bugs, banking regulation require constant work. Often the clock is ticking for old systems and asking vendors to provide and maintain ancient tools can be expensive or impossible. You can't "manually" move customers over, you need to "migrate" lots and lots of data - both systems will have huge, completely different database schemas.
- joncrocks 10y ago
- StillBored 10y ago$100 an hour, so $208k a year (assuming no time off), for a guy with 30+ years working on a critical system in an industry where floor traders can make 7-8 figures, and huge bonuses are paid to "analysts". I have plumber buddies that make more than that per hour (and with a crew can make more a year). That's why a couple years ago when I had access to a zseries, and was hearing about how "desperate" the banks were I took a look. What I discovered are salaries that are some of the lowest in the IT industry and a cynical attitude towards hiring. AKA, banks would rather pay $40k a year for a "system operator" which is generally the ground floor for learning anything about a mainframe than hire someone with a comp-sci degree and teaching them the system while promoting them. So, no thanks (you can fill in a less polite version), the banks can go to hell.
- movedx 10y agoNot sure if the $100/hour figure quoted is a hard and fast cash amount banks strictly adhere to, but ultimately this is business, so: set your price and walk away if it's not met. I set my price: AUD$850/day, with a TINY bit of wriggle room, and that's final. I know my worth (from a skills perspective and market/economical one.)
- fratlas 10y agoInc. Super/GST?
- movedx 10y agoNo. I don't receive that, the government does. That goes on top. Edit: misread. GST is NOT included in the price; Super is my problem and comes out of the agreed daily rate.
- nstj 10y agoYou could probably charge higher - this is at the mid range of many client side programmer daily rates in AU and systems skills like this are so much more critical.
- derrickdirge 10y agoBoy this sounds familiar. It's not just banks; many state (and presumably federal) angencies have this exact problem. The agency I work for now has a large COBOL code base that's been in the process of being converted to Java for a very long time now with varying degrees of success. I frequently have to read through COBOL to figure out what a particular project was supposed to do in the first place. It's not hard to understand, but it's certainly not immediately intuitive for someone who came up on Java. We have the privilege of still having a few of the authors of the original systems hanging around, but we won't for much longer.
- xacaxulu 10y ago"Experienced COBOL programmers can earn more than $100 an hour when they get called in to patch up glitches, rewrite coding manuals or make new systems work with old." $100/hr doesn't seem like a good rate for a true 'niche' when $185-$250/hr is going around for everything from Hadoop to Kubernetes.
- doggydogs94 10y agoJust went into Autozone and the interface looked like a IBM CICS screen scraper. Went to my insurance agent; we looked at nice screens, but when real money became involved, we popped into this ugly legacy screen.
- grogenaut 10y agoOr maybe it's because keyboard input is faster for a lot of heavily repeated form type things than a web interface. Web is nice when users don't know how to use it. When they do they're not really looking 1/2 the time.
- jlebrech 10y agoterminal screens needn't be old. they can be quite fast to operate.
- ltratt 10y agoMy gut feeling is that one can minimally maintain systems in "forgotten" languages indefinitely if they're basically stable and feature complete. But it seems that people come unstuck for systems that still need to evolve -- even if that evolution is slow and/or sporadic. The obvious alternative is to rewrite systems in new languages, but that is generally prohibitively expensive. Even for those that can afford the expense, the new system tends to not to take considerable time to bed in, so flipping the switch from the old to the new is only for the brave or those with excellent PR departments. Although we didn't have this in mind when we started on this work, I've come to think that language composition might offer a way out of this mess (I immodestly offer [1] as an early example). If one composes an old and a new language, one can migrate a system from an old to a new language bit-by-bit. As well as amortising the translation cost, it also means that one can minimise the "switch flipping" problem: disasters seem much less likely if the composed system can be introduced gradually. [1] http://tratt.net/laurie/blog/entries/fine_grained_language_composition.html http://tratt.net/laurie/blog/entries/fine_grained_language_c...
- Kiro 10y ago> Experienced COBOL programmers can earn more than $100 an hour Sounds low? That's what I'm charging as a web dev consultant.
- skc 10y agoI work at a large bank in my country. We have quite a few old gentlemen that work about four hours a day on insane hourly rates doing this sort of work. They seem to be living the life quite frankly, spending the rest of their day boating and what not. It's like the perfect retirement for them in that they get to stay challenged, get paid handsomely and still have most of the day to actually kick back.
- rmc 10y ago> Experienced COBOL programmers can earn more than $100 an hour Only $100 ph??
- jlebrech 10y agoyeah but you're holed up 7 days straight to fix something, so it quickly adds up.
- circadian 10y agoI used to work for a large multinational group whose core financial systems were written in COBOL during the seventies. I was told need to think of making the core systems future proof was identified as the company grew through the eighties and nineties, but never addressed. As time went by this attitude turned from one of "let's try and get on top of this" to "it can't be done because it's too risky / complex / old"... The net result of this is that this ignorance spilled into the attitude towards technology across the group. I found it very demoralising as you always had to fight to convince non-technical staff why they needed to address technical debt that was 10/20/30 years old. In the end I managed to undertake some big and interesting projects successfully in spite of the "you'll never achieve that without a disaster" attitude, but the core COBOL system were just ignored as if somehow it'd go away (the reality was much more political and complicated than that, as it is with all multinationals...) In the end I left for a position where people wanted me to build or rebuild things, rather than just spring the leaks around the problems. My point here is that unless you wield obvious experience or weight in this arena (as the "COBOL-legends" undoubtedly do) you'll have a job convincing people that it needs doing, at least until it goes up in flames.
- douche 10y agoBusinesses in general seem to have a really hard time dealing with training and institutional knowledge transfer these days. As an example from another industry, my father was working as a mechanic/greaser in a power plant for the past 17 years, alongside a millwright who had been there for 30, since they opened the doors. In the last six months, they both retired - after telling management what their timetables were about five years ago. The company never brought in anyone to train under them and learn all the minutia of how the plant works that is locked away in their heads. They haven't even hired anyone full-time to replace them. Needless to say, equipment all over the plant is starting to break down, because simple things like greasing bearings regularly isn't being done properly, and when things break down, they aren't being put back together properly, because no one knows the idiosyncrasies of the equipment. Every hour this plant is down costs tens of thousands of dollars. The millwright is starting to get called in as a consultant for three times his previous hourly wage.
- technofiend 10y ago>The millwright is starting to get called in as a consultant for three times his previous hourly wage. Sounds like he should have retired ten years ago. :-) :-)
- 0898 10y agoThere's a retail bank in London that still has its core standing order system written in pounds, shillings and pence with a translation routine sitting on top of it. It was supposed to have been rewritten as part of the millennium-bug investigations, but it never happened.
- ZanyProgrammer 10y agoAnd as long as you fit the "correct" demographics for living in the south.
- liveoneggs 10y ago> As of the 2010 census, the ethnic makeup and population of San Francisco included: 390,387 Whites (48.1%), 267,915 Asians (33.3%), 48,870 African Americans (6.1%), 4,024 Native Americans (0.5%), 3,359 Pacific Islanders (0.4%), 53,021 from other races (6.6%), and 37,659 from two or more races (4.7%). > Atlanta 2010 census: 211,365 Whites (38.4%), 28,071 Asians (5.1%), 286,126 African Americans (54.0%), ... So you mean.. what exactly?
- pc86 10y ago"Everyone in a red state is racist while I live in a post-racial utopia." Or something like that, I'd imagine.
- beat 10y agoIn the South, whites don't mind if blacks are around, as long as they're not uppity. In the North, whites don't mind if blacks are uppity, as long as they're not around. Segregation is worse in the north than in the south.
- splintercell 10y agoLol, I heard it differently, 'In South they are supposed to hate us in theory but not in practice, in north they are suppose to love us in theory but not in practice.'
- beat 10y agoI'm still waiting for the white people from the north to throw a fit because I said this. It's not always well received...
- unfocused 10y agoI dealt with something similar when I was a programmer. We had inherited a PDF publishing module written in 3B2 from the late 90s. (Google that language and you won't find much. Wiki article here: https://en.wikipedia.org/wiki/Arbortext_Advanced_Print_Publisher https://en.wikipedia.org/wiki/Arbortext_Advanced_Print_Publi...) The most I've personally seen a contract was for hiring a consultant to help fix bugs in this 3B2 language that nobody knew. The cost for bug fixing and onsite training was $5000 CDN, per day. That was back in 2010. The day was 7.5 hours so this guy's rate was $666/hour (Now that I look back, maybe that rate was an inside joke or something). We ended up hiring him for 5 days ($25K contract) as that was all that was needed to keep this module going, and we crammed a bunch of programmers in a room with him to see if we could learn a thing or 2 - the end result was negative. Nobody could learn it because we just didn't want to touch it. It took another 5 more years to kill off that module and move to an open source solution. Now before anyone does any straight math do see how much this consultant made per year, you have to understand that work was very limited, and eventually, everybody wanted this language and publishing software to die off.
- nraynaud 10y agodear Cowboys, start your ride in the morning, the towns are specifically spaced such that you can reach the next shelter in one day, avoiding the dangers of riding during the night.
- beat 10y agoI worked for years on the modernization of a critical banking infrastructure system. The problems are manifold. The biggest problem is overall architectural impedance mismatch - switching from a batch system (most of those old COBOL mainframe apps are batch systems) to a service-oriented architecture. This makes incremental replacement extremely difficult. But a cutover? On a system that moves more money in a day than the GDP of most countries? A failure could put the entire banking world in a tailspin, cause an economic crash. Next, there's a lot of business logic basically embedded in the COBOL, or even at lower layers. For example, lots of banking files are in EBCDIC, a different character set from ASCII. Except there are lots of different EBCDIC variants, and there's no good way to tell which one you're viewing just by looking at the file. So you have to reverse-engineer COBOL to figure out the "correct" meaning of a given file. The problems go on and on. When I see people in the startup world rolling their eyes at the "incompetence" of the enterprise world, I take it to mean they've never actually worked on a truly hard problem in their lives.
- fragmede 10y agoStartups have yet to solve the problem of legacy code. At the very center of Internet companies too old to still be called startups is some ancient Perl or PHP written by the founders, back when they were around, and even wrote code. That might seem less archaic than COBOL or faxes but it's the same root problem. "If it ain't broke, don't fix it" didn't account for "well you see, it's not catastrophically broken but it's holding us back"; maintenance programming isn't sexy, like maintaining bridges and highways that have already been built, but just as necessary for continued operation.
- ADefenestrator 10y agoYes and no. Some of the more successful "startups" like Google and Facebook have slowly rewritten the bulk of their systems over time. In the case of Facebook in particular, there's very little if any of the early scary spaghetti PHP left.
- wolfgke 10y ago> When I see people in the startup world rolling their eyes at the "incompetence" of the enterprise world, I take it to mean they've never actually worked on a truly hard problem in their lives. I worked in a related field in the past. I don't claim that the problems are easy - where I tend to roll eyes rather is: - Bureaucracy: A lot is required by law, I know. But there is a difference between "just following the required bureaucracy in a minimal necessary way if it stands in the path" (the startup way) vs. "taking it seriously in a way that makes the work harder than strictly necessary". - Hierarchies: Just three words: I hate them. - Unwillingness (?) to tackle these hard problems: The problems are hard, as you already outlined. But this implies to me that everybody in the company will move heaven and earth so that the people who work on this hard problems are able to (e.g. give all necessary information (requirement specification etc.) they know of etc.). If there is just one thing (or even office politics) which will prevent that, I don't just roll my eyes, but get furious. Because of the hardness this is not to consider an obstacle, but targeted sabotage - and should be considered as such.
- JimmaDaRustla 10y agoThe problem isn't COBOL developers, it's the Subject Matter Experts (SMEs) of the applications themselves - developers don't know why something was built the way it was, so maintaining and upgrading it is difficult from a logical perspective, not a technical one. When you provision a credit or debit card to an iPhone, it hits thousands of lines of COBOL for my bank. I wrote the application that delegates requests that come in on the payment network from Apple. Our issue isn't finding developers to maintain it, but if the application sits stagnant for decades, then the problem exists that we don't have product expertise to do the work.
- LurkerAbove 10y agoI had a recruiter contact me about a COBOL --> Java project a couple of weeks ago. I don't remember the $100/hour part though, seems like that would've stuck with me!
- killjoywashere 10y agoA couple of thoughts: If COBOL is such a big deal, a bank would get a steal of a deal if they funded some university chairs for professors who are willing to teach COBOL. "High Stakes Financial Software Engineering 332". Others are indicating that the banks would rather hire a novice and let them learn the system. Seems like they have some sort of long term onramp procedures. Or their current crop of almost retirees are harboring a deep-seated desire to see the world financial system go down in flames. Which would be odd for someone who will presumably be depending on a financial instrument like a pension or 401k for income.
- kazinator 10y ago"The call back to the bank was something of a personal vindication for me," he said. Being called back because nobody can figure out the undocumented hairball you left behind is a vindication? More like, your plan to ensure endless job security, having appeared to have faltered, was vindicated. You being vindicated means that someone admits that you should not have been let go; it was a mistake based on misinformation or whatever.
- y3sh 10y agoNot just banks, but large healthcare companies too. This is Accenture's bread and butter -- charging $120+/hr for analysts to reverse engineer COBOL into rules engines, then outsourcing a J2EE implementation. Last time I checked a large healthcare provider was paying over a million/month to maintain a mainframe claim processing system.
- surgeon7 10y agoInteresting how COBOL still stays relevant till this day. "They don't make 'em like they used to" is a cliche more commonly heard for hardware rather than of software.