Slashdot Mirror


51 Percent of Financial Services Companies Believe Existing Tech is Holding Them Back (betanews.com)

An anonymous reader shares a report: Legacy technology can be a major obstacle to digital transformation projects and, according to a new survey of financial services technology decision makers carried out for business consultancy Janeiro Digital, almost 51 percent say existing technology is holding back innovation. Three of the biggest roadblocks are seen as lack of support for change (34 percent), legacy technology and infrastructure (31.6 percent) and a lack of in-house technical skill (29.5 percent). As a consequence 23 percent of respondents believe their company is behind in digital transformation compared to others in the industry. Only 47 percent are currently implementing new technologies, with 12.6 percent wanting to do so but not having started. That leaves 40 percent not innovating which could see them lose out in a world where consumers want better, faster financial products.

141 comments

  1. Don't blame the tools by Revek · · Score: 5, Insightful

    Blame you're implementation of them. Improperly trained Bosses and ingrained static procedures often are the reason the tech you have isn't working for you.

    1. Re:Don't blame the tools by Revek · · Score: 4, Funny

      That and the packard bell you use for legacy applications.

    2. Re:Don't blame the tools by jbmartin6 · · Score: 1

      When half your resources go to babysitting applications which randomly break when "updating" or just for no reason at all, existing technology is definitely stifling innovation, and it has nothing to do with improper implementation. Source: I work in IT.

      --
      This posting is provided 'AS IS' without warranty of any kind, implied or otherwise.
    3. Re:Don't blame the tools by Revek · · Score: 1

      I often see people not using the systems they have to their full potential. Implementation if more than hardware. Training users on the use of their own system is also part of implementation.

      Source I also work in IT.

    4. Re:Don't blame the tools by Archangel+Michael · · Score: 5, Interesting

      The blame doesn't go for implementation, it goes for not understanding the opportunity cost of not doing something you should. When enough opportunities are passed, the businesses will cease to exist.

      I phrase it like this, "Good IT is expensive. Bad IT is costly".

      Do you have backups (expensive)? At some point it will cost you if you don't. It isn't a matter of if, but when.

      --
      Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
    5. Re:Don't blame the tools by tatman · · Score: 1

      Agreed. I work in fintech. The biggest obstacle is their own processes. Most banks (mostly the large banks) take a year to "certify" (aka test in house) software. I am aware of many customers still using WinXP, Windows 7 on their platforms.

      --
      I've always said English was my second language. Had Romeo and Juliet been written in C, I might have understood it.
    6. Re:Don't blame the tools by Archangel+Michael · · Score: 1

      Most people don't like pushing beyond what they are comfortable doing. They rarely go beyond that which they are familiar with. Training doesn't solve that problem, as it doesn't change the dynamic from "go to the freezer, get the box" to "I know this can do that, but I wonder how".

      IT people tend to be perpetually curious, which is why we often don't understand our users lack of curiosity.

      Source: I also work in IT

      --
      Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
    7. Re:Don't blame the tools by the_skywise · · Score: 2

      But the turbo button is pressed on my packard bell PC!
      Why isn't the app running fast enough?!

    8. Re:Don't blame the tools by KingMotley · · Score: 4, Insightful

      I suspect there's been 15-20 years of programmers telling the higher ups that they need to rewrite this stuff and the bosses saying they can't afford it/don't have to time to do it/won't hire the additional people to do it. All the while creating new non-standard tweaks to the system that has turned it into a big hairy ball of mess.

      Sucks to be them now.

      Source: I also work in IT, and deal with financial clients (Most of the big names).

    9. Re:Don't blame the tools by CodeHog · · Score: 2

      Agreed. And banks don't want to pay for good IT folks. Been there and hated it. I worked with one dev who took smoke breaks in the server room. They found it funny that I told them it damages the equipment. God I'm glad I left. Now I have to deal with in-house finance group but I can tell them to shove off when I want to.

      --
      Fat, drunk, and stupid is no way to go through life, son.
    10. Re:Don't blame the tools by Anonymous Coward · · Score: 0

      IT people tend to be perpetually curious, which is why we often don't understand our users lack of curiosity.

      Source: I also work in IT

      Users don't lack curiosity they simply have no motivation to be curious when it comes to tech. Leadership, which is just like them will excuse ANY lack of expertise from general staff but will raise holy hell if the technological people don't know every answer off the top of their head.

      Staff IS motivated to NOT understand tech because they aren't rewarded for learning and aren't punished for screwing up. Thus we end up with systems that don't change and cater to the lowest PERCEIVED common denominator. I say 'perceived' because the same staff and leadership have no problems with their own smartphones and the company payroll systems where they ARE motivated to understand how to use them.

      Source: I also work in IT

    11. Re:Don't blame the tools by ShanghaiBill · · Score: 2

      And banks don't want to pay for good IT folks.

      It is difficult for non-techs to tell "good" IT folks from "bad" IT folks. Why pay more when you can't tell the difference? Of course, you can tell the difference when things go wrong, but by then it is too late.

    12. Re:Don't blame the tools by Anonymous Coward · · Score: 0

      "Blame you're implementation of them."

      You implemented that possessive pronoun as a contraction. I blame you.

      PS: you're means you are.

    13. Re:Don't blame the tools by ShanghaiBill · · Score: 1

      I suspect there's been 15-20 years of programmers telling the higher ups that they need to rewrite this stuff

      When programmers are faced with maintaining someone else's code, they ALWAYS recommend throwing it all away and starting over. This is rarely the correct thing to do.

      Things you should never do

    14. Re:Don't blame the tools by MachineShedFred · · Score: 1

      I work on a team that maintains a financial application that talks to banks via ACH. I can't believe some of the restrictions they put on it, such as enforcing a single connection at a time, so we have to serially transfer 70+ files for various funds one at a time, waiting for an acknowledgement before the next one can start, and their systems take fucking forever to ack the thing.

      That job takes like 3+ hours to run, when it could take 20 minutes total if they allowed parallel connections, even with using IP-whitelisted password-protected certificate authenticated SFTP.

      --
      Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
    15. Re:Don't blame the tools by fluffernutter · · Score: 1

      If a person is hiring IT folks should that not be a fricking requirements of the job? I mean, we have all heard some of the ridiculous requirements they put on IT candidates, yet the person *hiring* them doesn't have to know ANYTHING about IT?

      --
      Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
    16. Re:Don't blame the tools by MachineShedFred · · Score: 4, Insightful

      This is a manager sickness - they don't see the difference between "operations" and "engineering".

      The operations people should be fighting those fires. The engineers should be creating long term solutions that prevent the fires to begin with. If your engineers are working a fire hose all day, nobody ever shuts off the fuel source and all you get is fires.

      --
      Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
    17. Re:Don't blame the tools by Anonymous Coward · · Score: 0

      Blame you're implementation of them. Improperly trained Bosses and ingrained static procedures often are the reason the tech you have isn't working for you.

      *your...

    18. Re:Don't blame the tools by Sperbels · · Score: 1

      Would you still be saying the same thing if you worked with me and saw the several million lines of VB6 code I maintain? VB6 isn't supported anymore. It's temperamental on modern versions of Windows. It's not like you can just continue running old versions of Windows indefinitely....well you could, but that comes with its own set of problems.

    19. Re:Don't blame the tools by Anonymous Coward · · Score: 0

      Is a "creimertard" someone who became retarded after reading one of your ebooks?

    20. Re: Don't blame the tools by Anonymous Coward · · Score: 0

      You idiot. I am your customer.

      I do not want tech innovation.

      Results in zeros on the wrong side of my balance

    21. Re:Don't blame the tools by frank_adrian314159 · · Score: 1

      Ultimately, that's true for any company that doesn't have techies up to the CEO level. At some point, someone who has no clue about IT will be doing the hiring of (at least) IT management.

      --
      That is all.
    22. Re:Don't blame the tools by Anonymous Coward · · Score: 0

      A creimertard is someone who copies and pastes the same drivel for months on end, becoming a bigger nuisance than creimer ever was.

      Especially on mobile devices.

    23. Re:Don't blame the tools by fluffernutter · · Score: 1

      So that's probably a big part of the problem then. It's not hard to learn things about IT. If they are the one getting paid bigger bucks than I (these days possibly hundreds of times more), then should they not know more about the organization they are running?

      --
      Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
    24. Re:Don't blame the tools by Anonymous Coward · · Score: 0

      Don't watch the video. You might find the LOTR reference baffling. Have you turned in your geek cred yet?

    25. Re: Don't blame the tools by Anonymous Coward · · Score: 0

      Go virtual for that use case ! Isolate it from Internet (truly isolated I mean )

    26. Re:Don't blame the tools by ShanghaiBill · · Score: 1

      It's not hard to learn things about IT.

      Yes it is. You need to know enough so that you can interview a candidate and tell the difference between someone who is competent and a BSer who knows all the buzzwords, has a surface level understanding of many things, and can even do routine tasks like "set up a VPN on this server", but is unable to troubleshoot complex failures.

      That is not easy, and even when interviews are conducted by professional IT managers, you are still going to get about 20% "bad hires".

    27. Re:Don't blame the tools by fluffernutter · · Score: 1

      Well fortunately this is a problem that isn't for us to solve. Perhaps corporations should recognize the people that know technology in their organization and involve them more in interviews. it doesn't sound like a very difficult thing to solve.

      --
      Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
    28. Re:Don't blame the tools by aberglas · · Score: 1

      VB6 is not all that bad, and it was madness for Microsoft to completely abandon it. A VBA programmer will have a project finished before a Java programmer can configure their Enterprise Application Server, or a C programmer can track down their obscure memory corruptions. .Net is better than VB6, but not that much better in practice. They could have walked VB6 forward. Added real compilation etc. Things like Set vs Let are historical oddities, but OK, and have an advantage of enabling a default value for objects.

      They also want to kill of VBA, but that will kill Excel.

    29. Re:Don't blame the tools by Anonymous Coward · · Score: 0

      Bonus:
      Here is a story that creimer told me when convincing me what a hard life he had:

      The tree was him and the tree knot was his butt hole!

      So, his uncle packed his fat ass with lard and with his cock! Not that it makes much of a difference but anyway, there it is!

      Signed:
      Ethell, The girl that used to love you and now hates you, burn in hell where you belong you sexist pig!

    30. Re: Don't blame the tools by Anonymous Coward · · Score: 0

      Blame the "permissive ToS" creamy dumpty bragged about (along with those pedophliac predilections). He still spams this site so Hes still hated. Suicide is not to be encouraged normally but...

    31. Re:Don't blame the tools by LostMyBeaver · · Score: 1

      haha last time I worked on ACH was in 1993... I was an 18 year old kid and the boss made me rewrite the ACH code in Visual Basic 3.0.

      What you just explained sounds a lot like the exact problems I had 25 years ago. We did however have a pretty cool hardware encrypted 4800 baud modem for it. Still, we were a data warehouse for several thousand banks and ATM machines. I'm pretty sure we spent between 8 and 10 hours a day transmitting and receiving batches.

      Tell me, is EDI-FACT in EBCDIC still the hot thing?

    32. Re: Don't blame the tools by Anonymous Coward · · Score: 0

      A BSer is trivial to detect if you have any business being in hiring. Whether IT, general contracting or an elective surgeon, you ask around and check references after you do a trivial screening.

      If screening isn't trivial for you, you shouldn't be doing the hiring.

      GP used vpn as an example. Explain VPN to me, in broad terms, then drill down after each level. If they can't get through basics without gobbledygook, and can't hit PKI wishing a minute and a half, they're not good communicators or just not qualified. Act accordingly.

      But the biggest problem in IT is everyone wants top quality candidates for less than average rates. Your own posts reveal that.

    33. Re: Don't blame the tools by Anonymous Coward · · Score: 0

      VBA is amazing. It is basically perl and python twenty years before they were around. I have used Excel as an IDE to do data analysis, machine translations, hell i even wrote what amounts to a progressive web app and backend site while also being a data entry ledger.

      It is a terrible process for the unskilled, but just because the bar for entry is so low doesn't mean it is the tool makers fault.

      If a client has a small budget, I'm not writing them a custom tool that does exactly what they need when they prefer to stick with the Excel abomination they already know, because that already works for them. Don't reinvent the wheel if they have a training budget of zero.

    34. Re:Don't blame the tools by Pig+Hogger · · Score: 1

      That and the Data General you use for legacy applications.

      There, fixed it for you.

    35. Re:Don't blame the tools by Pig+Hogger · · Score: 1

      I often see people not using the systems they have to their full potential.

      Oh god. I stopped counting the times I got shit for putting some user’s 17 inch CRT to 1024 x 768 resolution up from their customary 800x600...
      “Everything is too small!”...

    36. Re: Don't blame the tools by Anonymous Coward · · Score: 0

      C.D. Reimer is a renowned Slashdot collaborator, as he puts it himself; "Because of the quality of my posts and my article submissions, I'm a highly rated commentator and moderator."

      But does anybody ever wondered what "C.D." stands for? Well, it stands for Creimy Dumpty of course!

      Creimy Dumpty sat on the wall,
      Creimy Dumpty had a great fall.
      All the king's horses
      And all the king's men
      Couldn't put Creimy Dumpty
      Together again.

      Creimy's siblings video and theme song, very realistic, especially the pants, just like Creimy's:
      https://www.youtube.com/watch?...

      With "Vice President Pence Vowing US Astronauts Will Return To the Moon", we are sure they will need miracle workers up there, here is what it would look like. Note that Creimy takes care of bringing a lot of food to the moon as depicted below:
      https://www.youtube.com/watch?...

      Creimy's real pictures:
      Before the sex change:
      https://ibb.co/cc7Ddw
      After the sex change:
      https://ibb.co/gVad65

      Creimy's "enterprise-level" chair, he talks about it all the time on slashdot:
      http://www.keynamics.com/image...

      Creimy's head, while his supervisor was talking to him, not with him, since it is impossible to do with Creimy:
      http://ibb.co/mRVSaG

      Creimy acting in educational resource document, he actually confirmed himself on Slashdot that he was handled by Special Education for the Santa Clara County Office of Education! He is really a king Dumpty!:
      http://www.sccoe.org/depts/stu...

    37. Re:Don't blame the tools by Pig+Hogger · · Score: 1

      Users don't lack curiosity they simply have no motivation to be curious when it comes to tech.

      Jesus. When I started working (in IT), users were afraid they’d get electric shocks when you introduced them to the computer terminal...

      But it was kinda a blessing, because the most enthusiastic users were the ones who would fuck up things... Heck, I once saw a financial analyst dance of joy, calling himself “space cadet” when I finished installing a CP/M computer in his office...

    38. Re:Don't blame the tools by Pig+Hogger · · Score: 1

      "Good IT is expensive. Bad IT is costly"

      Was it the president of Harvard who said “You think education is expensive? How about ignorance?”...

    39. Re:Don't blame the tools by Pig+Hogger · · Score: 2

      I worked with one dev who took smoke breaks in the server room.

      I once worked for $BIG_CIGARETTE_MANUFACTURER. On the IBM mainframe computer CPU cabinet was a big ashtray with a sign “thank-you for smoking”...

    40. Re:Don't blame the tools by ShanghaiBill · · Score: 2

      Would you still be saying the same thing if you worked with me and saw the several million lines of VB6 code I maintain?

      Yes. "Starting over" is almost certainly a mistake. That codebase handles much complexity and covers many corner cases that you likely fail to appreciate. It isn't complex because it is "bad code" but because it is solving a complex problem. By starting over, you will need to build and budget for a new team. One team to maintain the existing codebase, while another team works on the new code. Soon you will have this problem, as every change and new feature has to duplicated in both codebases. People will grow frustrated, and quit or transfer to other projects, taking their expertise with them. As the "vision" people leave, and the remaining coders are under pressure to get stuff fixed, the new code base will start to fill up with hacks and workarounds. Then a new manager will take over and ask what should be done. The programmers will unanimously reply: "Throw it all away and start over".

      Instead of "starting over" here is what you should do:
      1. Set up a VPS, with the best OS and all the development tools. Snapshot it onto a thumb drive. Now you can always rollback to a working system.
      2. Set up a Git repository, and use it. Now you can track changes and rollback with much better granularity.
      3. Set up a bug database.
      4. Build a test suite.
      5. As you fix bugs and add features, start commenting and refactoring the code. Refactor where the bugs are.
      6. After every bug fix, add a regression test to the test suite. TDD & FBF.
      7. Once the code is mostly refactored and cleaned up, then, and only then, should you start shifting to a new platform. Make sure you can do it incrementally, the way Johnny Cash built his Cadillac: one piece at a time. This means being able to make function calls from VBA into your new platform (maybe C#?) and vice versa. Run your automated suite after every significant change.
      8. Use "continuous deployment". Don't roll out lots of big changes all at once, and alienate your users, but instead make lot of small changes regularly. Very importantly make sure the early changes are things the users WANT, like bug fixes and GUI improvements. This will give you stakeholder buy-in and build up karma that you can cash-in when problems arise.

      Good luck.

    41. Re:Don't blame the tools by Anonymous Coward · · Score: 0

      This is usually because they rewrite only small part of the system or the whole system, but without fixing the big architectural problems.

    42. Re:Don't blame the tools by Billly+Gates · · Score: 1

      I blame outsourcing.

      Banks ARE CHEAP and hire Indian kids for programmers and infrastructure and pay them $15/hr to code and maintain the systems.

      When you feel $30,000 is all a senior level developer is worth they won't bother upgrading them. After all they work fine right??

      Now a good Wall Street trader? Now that generates revenue according to the executives

    43. Re:Don't blame the tools by Anne+Thwacks · · Score: 2

      I think you will find banks had computers since the 1950's, and had version control even then. They certainly had it in the 1960's. It was built in to the editors used with mag tape.

      --
      Sent from my ASR33 using ASCII
    44. Re:Don't blame the tools by Anonymous Coward · · Score: 0

      Your entire YouTube presence is baffling, Chris.

      Here's another baffling thing about you; you latch on to incorrect expressions and won't let go even when shown you're wrong.

      Go ahead, google for "turn in your geek " and watch how it auto-completes.

      But the one thing you have over me is that your face is your geek card.

    45. Re:Don't blame the tools by nasch · · Score: 1

      I don't know that much about it, but would that be all that difficult to migrate to VB.NET?

    46. Re:Don't blame the tools by Anonymous Coward · · Score: 0

      I often see people not using the systems they have to their full potential.

      Oh god. I stopped counting the times I got shit for putting some user’s 17 inch CRT to 1024 x 768 resolution up from their customary 800x600... “Everything is too small!”...

      So what? Some people's eyesight doesn't deal well with higher resolutions. If I was using a 17" monitor I probably wouldn't be using it at 1024 X 678 either. Hell, I have a 32" monitor that I'm only running at 1920 X 1080, when it's capable of 2560 X 1440. The 'full potential' being discussed here is about using the features that the software provides to increase efficiency and ease of use. It's not about monitor resolution.

      -- jenningsthecat

    47. Re:Don't blame the tools by KingMotley · · Score: 1

      That is a good approach to take for some projects. Unfortunately, not others. Like a certain company I know who has 20+ clients, all running what should be the same code, but it's 20 different COPIES of code in various stages of development. Try getting that under control, lol.

      The code base isn't very TDD friendly. Like there are routines that are 50,000+ lines long, which basically does everything. And there are 20+ copies of that routine, that are all slightly different, most of the time for no reason other than 3 different people wrote the same logic 3 different ways -- all of which are terrible... 20-30 lines of code that is hard to read with edge case bugs, and can be rewritten in 1-3 easy to read line with no edge case bugs, but trying to find out if those edge cases are really bugs or just bad code is nerve wracking. One out of 20 times, yes, there really was a edge case that needed that not so easy to see side effect. The entire code base is that way. So we're refactoring what we can, modularizing it, and then breaking those modules out into standard libraries and then re-integrating those libraries into each of the 20 clients. Long, and painful.

      It is a LOT more painful than just starting over, and then attempting to migrate all the clients to the new code base one at a time. Starting with a code base that is TDD/Unit Testing friendly. However, that is a 6-9 month project before you see any tangible results vs the long and painful way which will likely take us the next 5-6 years and when we are done it won't be nearly as nice. But... managers and owners like to see stuff NOW. Even if it's crap. I just hope that support isn't dropped from our old frameworks before we get a chance to get off them.

    48. Re:Don't blame the tools by Anonymous Coward · · Score: 0

      Oh you browse below one on mobile devices? Which mobile browser do you recommend?
      I have good reason to believe you're lying so let's hear your answer so I can bust you out!

    49. Re:Don't blame the tools by Anonymous Coward · · Score: 0

      Go ahead, google for "turn in your geek " and watch how it auto-completes.

      You must be new around here. All the old timers on Slashdot use "cred" for that expression. Only a noob would use Google.

      Do the community a favor and turn in your geek card.

  2. Clearly the answer is by Anonymous Coward · · Score: 0

    More and better cryptocurrencies.

  3. According to same companies, 51 percent regulation by Anonymous Coward · · Score: 0

    holding them back. See what they do there?

  4. So they made a conscious decision not to upgrade by QuietLagoon · · Score: 1

    And now they are complaining because their infrastructure has become "old" and difficult to maintain. Sounds to me as if they just want to blame something else for the bad business decisions they made.

  5. They only have themselves to blame by Pig+Hogger · · Score: 4, Insightful

    They’re the source of their own problem. Whenever they manage to hire brilliant people, they hold them back with arcane process and lengthy byzantine procedures (mostly enacted to internally cover the bosses’ asses).

  6. This is not hard by PopeRatzo · · Score: 5, Insightful

    Instead of complaining about legacy tech "holding them back", maybe these "financial service" companies should invest in some better tech instead of using those record profits for stock buybacks and bonuses to C-level management. You've been eating out on the backs of taxpayers all through this last decade of the government giving you free money. Maybe it's time to do something that won't, you know, bring down the fucking economy again.

    Just a thought.

    --
    You are welcome on my lawn.
    1. Re:This is not hard by Narcocide · · Score: 2

      You might as well ask caterpillars to tend your flower garden.

  7. Another crap tech article by Anonymous Coward · · Score: 1

    Just more crap. They state lots of exact percentage numbers, but talk 100% vague about "legacy technologies". Please define "legacy technology".

    And please be very specific about 1) what you're using now, 2) what / how you're being limited, and 3) what the new advanced world-saving technology is and how it will solve all of your (perceived) problems.

    Then I will tell you about how much productivity you'll lose while people 1) sit in "training" classes, 2) have problems opening up that old document, .xls, etc., and 3) how these "new technologies" actually slow us down.

    Case in point: a year or so ago I "upgraded" this very computer to Win7 from XP. XP was great because I could click on the lower-right network icon and get right to "properties". Now I have to click more times, go through several windows, etc. Time wasted. Stupid. Going backwards we are.

    1. Re:Another crap tech article by xxxJonBoyxxx · · Score: 2

      >> a year or so ago I "upgraded" this very computer to Win7 from XP

      Really, no takers? I thought this was one of the best pieces of troll bait to be spun through Slashdot this month.

    2. Re:Another crap tech article by Anonymous Coward · · Score: 0

      You only waited 26 minutes. 26 minutes during the after lunch slow down. You have to let the troll bait linger a bit.

    3. Re:Another crap tech article by Anonymous Coward · · Score: 0

      I'm curious, what are some of the types of troll comments you thought people might make?

    4. Re:Another crap tech article by xxxJonBoyxxx · · Score: 1

      Well, first note that XP went EOL in 2014, and that the large number of XP computers still out in our networks continue to plague a number of IT professionals on SlashDot who have to support them. And note that many IT professionals who have to support desktops consider Windows 7 to be the best of the desktop OS's.

      Now combine that with a biting comment from a Windows XP footdragger who doesn't like Windows 7 (with "upgraded" literally in quotes) and you have some grade-A SlashDot trollbait.

  8. Brokerage software and Beta by Hadlock · · Score: 3, Informative

    I used to work for a finance company deploying and automating the deployment of finance software. There's a couple I know of. Talisys out in Denver is one, but the 800 lb gorilla is a piece of software called Beta. It's freaking ancient. Like, core parts still in use today are from the 1970s. I think they've written some API front ends for it, but you have to pay through the nose for every feature, and especially for the fancy features. Beta was written... back in the 1970s perhaps? It doesn't lend itself to modern development methods very well. But it works and has a solid, proven track record, which is exactly what risk adverse finance companies like, especially when they are signing four and five nine uptime SLAs. Talisys is a little newer, developed in the early (1992?) 1990s and came to market around 2002 as production ready, but it's still based on 1998 era technology and were crawling in to the modern age offering Windows Server 2012 R2 support in 2015. There was actually a two year gap between when WS 2003 microsoft windows extended service support ended and when they supported a newer version of windows (2012 R2) and yes you read that right some big (not huge) companies are running financial software on top of Windows.
     
    Other financial technology companies like Robinhood are written cloud-first and cloud-native with APIs in languages like Python and Go and Ruby and what have you. They're just going to eat up these old companies as their overhead costs are much lower and their code better documented and aligned more closely with modern programming practices. Their most modern competitors are running windows software designed in the 1990s. It's ripe for disruption and companies like Robinhood are absolutely going to grind these old companies in to a fine paste in the next ten years.

    --
    moox. for a new generation.
    1. Re:Brokerage software and Beta by Anonymous Coward · · Score: 0

      Can't tell if I'm reading an ad for Robinhood.

    2. Re:Brokerage software and Beta by goose-incarnated · · Score: 4, Interesting

      Other financial technology companies like Robinhood are written cloud-first and cloud-native with APIs in languages like Python and Go and Ruby and what have you. They're just going to eat up these old companies as their overhead costs are much lower and their code better documented and aligned more closely with modern programming practices. Their most modern competitors are running windows software designed in the 1990s. It's ripe for disruption and companies like Robinhood are absolutely going to grind these old companies in to a fine paste in the next ten years.

      No, they are not. It's easy to start a system from scratch regardless of the language you are using. Let robinhood get to the 10-year mark with their only-break-at-runtime-because-look-ma-no-compilation-step python software and they'll be crying for someone to buy them out.

      It looks easy when you first write the software, but let's see how resistant to breakage it is after 10 years of maintenance when half the code was written by people who weren't part of the original team. Their brand-new system of $X kloc of python+ruby probably works well enough with the existing specs. I want to see how well it works when changing requirements cause that codebase to balloon to $(X * 3) in ten years.

      Even worse, you're complaining about the current systems being written in obsolete languages; FFS Ruby is *already* obsolete and it's in their *new* system!

      --
      I'm a minority race. Save your vitriol for white people.
    3. Re:Brokerage software and Beta by Anonymous Coward · · Score: 0

      They're just going to eat up these old companies as their overhead costs are much lower and their code better documented and aligned more closely with modern programming practices.

      This is exactly what Talisys thought when they developed a PC based system to replace the mainframe based systems. It wasn't quite as easy to displace the old dog as they thought.

    4. Re:Brokerage software and Beta by Pig+Hogger · · Score: 1
      — sigh —

      30 years ago, I had a job maintaining Business-Basic programs for an non-IT company. It was okay, and I ran around Business-Basic limitations by writing a "pre-compiler" (a bit modelled after "CPP") that enabled the use of long variable names and labels instead of line numbers. Over the time, the final Business-Basic source-code was pretty well documented so you could work without the pre-compiler.

      Then I left for other pastures, never to return.

      About 5 years ago, I took a Business-Basic gig where I had to maintain old code (heck, it paid $45/hour), as the guy in charge of it was dying of cancer. But in 25 years, Business-Basic had evolved; it got long variable names, labels, functions, procedures and even objects! Wow wee!

      So, when I was handed a program to fix, it was old legacy code, as it was written 40 years prior. The variable references were all listed in a series of binders full of dot-matrix faded dog-eared sheets of paper full of hand-written notes in some pre-glagolitic script.

      After spending a week making sense out of the spaghetti (and billing them upwards of $2000) where I have given meaningful names to variables and properly labelled the program branch points and subroutines (functions? Ha!), I was told to stop doing this “because we have standards”.

      But just as I was going to tell the dude to shove his job where you thin, he asked me if I could do a much more urgent project: converting XML data from a 15 year old application to import in a 40 year old application. So I took my sweet fucking time writing it in Python (ha!) for a good month and a half. What helped is that the dude was working in a “okay, let’s do this”. Then when you’re through “Oh, and it should also do this”, and so on for several weeks...

      This year, I took a 4 months vacation far enough to not be bothered by phone calls...

  9. more like... by swan5566 · · Score: 2

    ...their unwillingness to invest in upgrading it, because it will affect the bottom line in the short term.

    --
    In debates about Christianity, there are two groups: those looking for answers, and those looking to just ask questions.
  10. Really? by AlanBDee · · Score: 5, Insightful

    So a consulting company held a survey and found that 51% of companies believe that legacy technology is the biggest hurtle they face. That's good news for this consulting company that sells "solutions" to that problem. Oddly enough, my banker thinks I need a credit card and that car salesman insists that my old (2007) car is about to fall apart and I should buy a new one.

    Legacy technology and technical debt is a problem that is often overlooked and not budgeted for because it won't affect the stock price this quarter. Still, forgive me if I don't believe that this survey accurately outlines the problems that companies actually have to this degree.

  11. That God! by plopez · · Score: 2

    Their definition of "Innovation" is ripping more people off faster with financial shell games. Anything that impedes the "financial services" sector from "innovating" is a good idea.

    --
    putting the 'B' in LGBTQ+
    1. Re:That God! by HiThere · · Score: 1

      Well, there's more than one kind of business that could be called "financial services". For a certain kind of "financial services" your description is quite apt, but I guess I was thinking of a different segment...which still isn't anything that I think highly of, but which doesn't merit wholesale condemnation.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    2. Re:That God! by plopez · · Score: 1

      I was talking banks and brokerages. They do not have customers, they have marks. It makes more sense to keep your money under a mattress these days than in a bank

      --
      putting the 'B' in LGBTQ+
  12. We need more Blockchain!!!!!!!! by ErichTheRed · · Score: 1

    Serverless Blockchain Containers orchestrated by Kubernetes and deployed by Jenkins, Terraform, Vagrant and friends are the savior the financial sector needs!!!!!! Buy CloudWeasel CI/CD today! Any workload, any toolchain, any cloud!

    (OK, in all seriousness...if they're talking about mainframes and COBOL underpinning almost everything they do, I might agree.) This just sounds like a study by a consulting firm [[looks-- oh yes, it is!]] planting the seeds of doubt in executives' heads to get the purse strings loosened. Traditional companies are totally in Fear of Missing Out mode and the consulting companies are cashing in on that.

  13. Regulations are holding them back by rsilvergun · · Score: 3, Insightful

    there are rules about how they change their tech to keep them from pulling all sorts of tricks and shenanigans with their software. They're hoping to make those rules go away. Believe me, you do not want this. Yeah, you'll get your new tech, but you'll get an unstable financial system and a crash that makes 2008 look like a happy memory.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
  14. Faster and better? by Anne+Thwacks · · Score: 3, Insightful
    I think not.

    What consumers/customers want (even if they don't know how to pronounce it) from financial products is:

    • security - as in not having their data leaking all over the place
    • privacy - as in not having their data sold to anyone who pays
    • not to be ripped off
    • clarity - as in being told the truth about what they are paying for
    • honesty (yes, I know they won't get it, but its what they want).

    So, in other words, not to have to deal with financial institutions at all.

    --
    Sent from my ASR33 using ASCII
    1. Re:Faster and better? by Anonymous Coward · · Score: 0

      When I invest in the stock market, I'm interested in return OF my investment, not return ON my investment.

      - Mark Twain

    2. Re:Faster and better? by nine-times · · Score: 1

      I think that assessment might be a bit generous to consumers. They only care about security after they've lost money. They only care about privacy after sensitive information has leaked. They only care about clarity when they start to suspect they're being ripped off. They only care about honesty when they discover they're the ones being ripped off.

      What most people want from financial products is a fail-safe get-rich-quick scheme. They'll turn a blind eye to a lot of problems as long as they think they're getting rich.

    3. Re:Faster and better? by SirGarlon · · Score: 1

      What most people want from financial products is a fail-safe get-rich-quick scheme. They'll turn a blind eye to a lot of problems as long as they think they're getting rich.

      I don't know about "most people," but I do think you've identified a population. As P.T. Barnum said, there's a sucker born every minute. And I'm sure there is a legion of financial "service" firms ready to take advantage of an easy mark.

      --
      [Sir Garlon] is the marvellest knight that is now living, for he destroyeth many good knights, for he goeth invisible.
    4. Re:Faster and better? by Anonymous Coward · · Score: 0

      I think not.

      What consumers/customers want (even if they don't know how to pronounce it) from financial products is:

      • security - as in not having their data leaking all over the place
      • privacy - as in not having their data sold to anyone who pays
      • not to be ripped off
      • clarity - as in being told the truth about what they are paying for
      • honesty (yes, I know they won't get it, but its what they want).

      So, in other words, not to have to deal with financial institutions at all.

      So you DO want better....

      faster...

      When you get down to the nuts and bolts of things behind your bullet points, nothing is as simple as it sounds, and change takes time

  15. Re:So they made a conscious decision not to upgrad by freeze128 · · Score: 2

    And they also complain that they have a lack of in-house technical skill. The longer you work with your technology that has become old, the more skilled you will become at using it. Changing it too often just leads to chaos.

    Unless, what they meant was that they had a lack of *IN-HOUSE* technical skill, in which case, stop outsourcing it!

  16. That's not innovation by Anonymous Coward · · Score: 0

    Innovation is not an annual goal to achieve.

    Innovation is a response to an unmet need or a pain point.

    Innovation how you respond to that legacy roadblock: avoiding it, finding a better way, or removing the need for it altogether.

    Those that report tech IS the roadblock aren't going to Innovate anything.

  17. Re:So they made a conscious decision not to upgrad by Narcocide · · Score: 3, Interesting

    They're gonna keep complaining like this until someone makes a computer that will learn to use itself. Then they will complain that it isn't fast enough.

  18. Ahh... another one by rnturn · · Score: 1

    Consultancy specializing in "digital transformation" (i.e., popular new buzzword) does self-serving survey that miraculously finds that their services are needed.

    I especially like the finding that 29% of companies are whining about not having the needed skills in-house. I predict that the survey did not ask companies whether they were investing in any training for their IT staff and, if they had, the responses would range from "Hell, no!" or "No" to "Huh? What is this `training' thing you asked about?"

    --
    CUR ALLOC 20195.....5804M
  19. Probably not wrong by nine-times · · Score: 1

    I'm not much of an expert in finance, but I know a fair amount about IT, and I'd say it's a safe bet that crappy technology, legacy tech, and vendor lock-in is holding back a lot of efficiency and innovation.

    I mean, technology in general is adding a lot of innovation and efficiency. For sure. But I see a lot of businesses depending on some weird custom-built application that was built in the '90s and doesn't support any OS past Windows XP. I see a lot of simple, common problems going completely unaddressed, while all the computing talent is focused on building the next crappy Snapchat clone. Microsoft seems intent on using all of their expertise on forcing advertising down everyone's throat. Apple is just making things thinner and lighter without making them more useful or reliable. The FOSS community is so wrapped up in everyone reinventing their own wheel, and so you end up with a bunch of half-finished clunky wheels.

    It kind of makes me regret that I gave up programming, because maybe I could fix some of these problems. Of course, if I hadn't given up programming, I'd probably have just ended up being yet another person trying to develop a Snapchat competitor rather than fixing real problems.

    1. Re:Probably not wrong by fluffernutter · · Score: 1

      A company has really got to acknowledge it is an issue and put money behind it before it does any good. We always see these kinds of whiny articles. It's like a dysfunctional person complaining that it's too hard to quit drinking alcohol every day. We can 'aww' and 'pooh pooh' them all we want, but at some point the only person that can fix it is the corporation.

      --
      Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
    2. Re:Probably not wrong by Anonymous Coward · · Score: 0

      But I see a lot of businesses depending on some weird custom-built application that was built in the '90s

      I make a nice amount of money supporting and maintaining my weird custom-built application that was built in the '90s. I call it my creaky little digital cash cow.

  20. COBOL by Anonymous Coward · · Score: 0

    Cry
    On
    Bitches,
    Obsolescence
    Lives!

  21. I think they donâ(TM)t understand financial s by Anonymous Coward · · Score: 0

    The financial services companies that is. The people that came closest to actual understanding are probably in jail, in non-extradition treaty countries, retired or dead.

    Tech isnâ(TM)t going to save those that remain.

  22. In other words, by Anonymous Coward · · Score: 0

    51% of Financial companies are too cheap to upgrade their systems.

  23. The REAL patented problem. by geekmux · · Score: 2

    The real problem is not existing products destroying innovation.

    The real problem is patent hoarding destroying the ability to innovate altogether.

    Go ahead. Try and invent something. I dare you.

  24. Blockchain v. Checksum by Anonymous Coward · · Score: 0

    Ask a blockchain proponent/developer in the finance space what the difference between their precious blockchain project and a checksum function is. If they can explain it they are entitled to an opinion on this stuff. 99.99999% of them cant. The vast bulk of the people working in financial innovation space wouldnt know innovation if it bit them in the you know where. The industry's big move to blockchain is primarily them using blockchain for checksum and version control functionality. Oh, what an innovation.....

    1. Re: Blockchain v. Checksum by Anonymous Coward · · Score: 0

      But but but blockchain , buddy ! Come on, it has to be good if it has a blockchain!!!

  25. More and more tired old tropes by rickb928 · · Score: 4, Interesting

    I deal with tech a lot where I work, an instantly recognizable financial business.

    Our core transaction processing systems run COBOL. When your Python app can settle as few trillion transactions nightly with deadlines met within minutes and downtime measured in seconds per year, present it. Someone will listen.

    The stuff I deal with daily now uses Cassandra for a db backend, all is hosted within LAMP stacks (we said goodbye to WebSphere a while ago), and is tolerating all major browsers for internal and external users. Our constraints aren't tech, they are resources; we decide to support a certain range of demand, and so size the systems according to budget. When our users begin complaining, we will resize.

    I've noticed a bunch of internal apps moved to interesting containers, and using two- or three-factor authentication. Our security methods treat employees as strangers, and internal systems as threats. Nothing is trusted until it is authenticated, carefully. This security problem is the source of much of the apparent lack of innovation in the industry, as we where I work are a top 50 target. Maybe top 10, we have not been told of a breach. We spend as much on testing our security as we do on the security.

    Our single biggest repository is on a custom Linux system, some our own software. It handles the volume you would associate with Google. It has to be secure.

    And we of course have document storage, but that's on old stuff based on Wang systems, which you cannot outperform yet. No you cannot.

    Yet we are faced with demand for flexibility, new and innovative solutions to new problems, and creative products. We've delivered a blockchain based international settlement system with a respected partner, at the same time as we've spun off a product that made all the sense in the world but didn't sell and are turning off one that just isn't working for anyone.

    A previous CIO lamented that a third of our projects failed. That's actually pretty good in the business world at large. But it's really not good enough. And new tech by itself will not do it. Better planning, better management, and better infrastructure will. And we are building those. I can name a few competitors that are clearly not, and I relish the opportunities we have to drink their milkshakes.

    --
    deleting the extra space after periods so i can stay relevant, yeah.
    1. Re:More and more tired old tropes by Picodon · · Score: 1

      We spend as much on testing our security as we do on the security.

      Not being in that field, I’m curious: does your company share (both as provider and recipient) methodology information (security best practices, etc.) with others in the financial sector (or with an even wider audience) or is it something that is considered somewhat secret (competitive advantage, etc.)?

    2. Re:More and more tired old tropes by Pig+Hogger · · Score: 1

      There’s nothing wrong with COBOL, as long as it works as it should.

    3. Re:More and more tired old tropes by Anonymous Coward · · Score: 0

      The problem with legacy languages is that "it works as it should" is not a stationary point. What is needed over time often changes.

      This means that any language that doesn't embrace and support modern development processes and methodologies is at a disadvantage. COBOL is even worse in this regard, because I have to train the not-up-to-date with outside technology COBOL workers to work in a modern environment, or have to hire current professionals and train them in COBOL, or have to hope that there's already a few that meet both requirements.

      Where are the COBOL unit tests? Where is the COBOL code coverage tools? How do I do Continuous Deployment with COBOL? I'm sure that it can be done in some way, but COBOL is so far out of the mainstream I wouldn't be surprised if there wasn't, or it wasn't followed in many environments.

    4. Re:More and more tired old tropes by rickb928 · · Score: 1

      Competitive advantage. I do not know if we share within other security forums, probably yes, when we see either dangerous new methods, but we do not share anything proprietary unless it were a known industry-wide problem and we saw a duty to share.

      --
      deleting the extra space after periods so i can stay relevant, yeah.
    5. Re:More and more tired old tropes by Picodon · · Score: 1

      Interesting, thanks! I understand the business rationale, and I can also imagine the difficulty to share methods that could reveal too much about one’s infrastructure, or could be too specific to an architecture to be broadly applicable to others. At the same time, as an outsider, I find it striking that mistakes seem to be endlessly repeated (by different entities) and I also imagine that those mistakes have the potential to fragilise not merely those who make them but to also spread to partners, suppliers and customers. In most fields, methods eventually mature and propagate as specialists move from one company to another; in this field, though, with new technologies and new threats seemingly appearing every week, I am not expecting spontaneous maturation to have much impact. On the positive side for security experts, that makes them all the more valuable!

  26. There's yer problem by Anonymous Coward · · Score: 1

    Three of the biggest roadblocks are seen as
    lack of support for change (34 percent),
    legacy technology and infrastructure (31.6 percent)
    and a lack of in-house technical skill (29.5 percent).

    Item number 1 is a symptom of item number 2. Item number 2 is a symptom of item number 3. Item number 3 is a symptom of outsourcing everything to India.

    You get what you pay for.

  27. Not so by Archtech · · Score: 2

    "That leaves 40 percent not innovating which could see them lose out in a world where consumers want better, faster financial products".

    Actually, it turns out that consumers want a good life; a happy, healthy family and friends; interesting work that (ideally) helps others; respect and appreciation; healthy, tasty food and drink; plenty of interesting exercise and sporting activities; enough money to enjoy all those things...

    "Better, faster financial products" come absolutely nowhere on the list of things that sane, sensible, well-balanced consumers want.

    --
    I am sure that there are many other solipsists out there.
  28. skill by fluffernutter · · Score: 2

    a lack of in-house technical skill (29.5 percent)

    It's a free market. Keep bumping up the offer until you get what you want. If the market isn't working for you then you're not trying hard enough.

    --
    Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
    1. Re:skill by Anonymous Coward · · Score: 0

      what's good for the company (or shareholders) is often not in line with what's good for the individual managers.

      e.g. often middle managers need to fill a chair, because they got budget for a ``resource'' (they're people, damn it!). the more resources they manage, the more important their rank is within the organization. holding out for the right candidate only moves those budget dollars to another department that didn't hesitate to hire a warm body.

    2. Re:skill by fluffernutter · · Score: 1

      It is still all their choice to run their business that way Just like if I decided to drop out of school and do nothing but play video games, then complain that I have to work for minimum wage on Slashdot and all my jobs are going away due to automation, someone would be quick to give me the cold hard truth that I must either strive to improve myself or be happy with minimum wage. Well, if companies choose to continue running this way, then they had better be happy with it as well. Why do we indulge them when they shrug their shoulders and say there is nothing that can be done on their side?

      --
      Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
  29. They hold themselves back by Anonymous Coward · · Score: 0

    They have not been paying or hiring technical talent for years. They do not listen to us when we describe proper architecture and instead insist we use insane technologies like .net instead of javascript for web applications. They underpay us, hell I've been working almost my entire career being paid the same as a fry dipping teenager at mcdonalds and yet creating software that they couldn't hope to find or create any other way.

    Then they insult us by hiring foreigners who quite frankly just don't have the chops to do the work properly.

    Companies in north america need to get their heads out of their asses, listen to their technical team and give us the resources and time to create the systems they need properly.

  30. Re:So they made a conscious decision not to upgrad by QuietLagoon · · Score: 1

    ...And they also complain that they have a lack of in-house technical skill. The longer you work with your technology that has become old, the more skilled you will become at using it....

    Unless those who have the technical skills start retiring. (think: COBOL)

  31. Larger problem by sgrover · · Score: 2

    The technology is only part of the issue though. Organisational politics are a major factor. But then there are the hidden issues too. Such as "our order flow system does X, y, Z, and a,b, and in some cases c." Each of those areas has subtle and often undocumented/unspoken requirements and interdependencies. Replacing the overall system is highly desirable, but nothing can meet all the requirements out of the box, and sometimes modifying or building a system has extreme costs with zero benefits. I mean why pay a large amount of cash to get a system that does exactly what we have now, just so we can say we have modern technology. How do you justify that expense to shareholders and/or customers. And because the issues is large and ill-defined, managers would rather focus on the smaller well defined issues they have on their plate. There are better ways. But it's a judgement call if it is in a company's economic best interest to embrace the pain of adopting that better way.

    1. Re:Larger problem by sjames · · Score: 1

      Of course, they've often forgotten that their existing workflow is the way it is to accommodate the limitations of the old tech and the limitations of paper processing before that. Yet, somehow even minor changes are off the table even if it means the difference between using something off the shelf or either spending a fortune in modifications or spending a fortune on spit and bailing wire to hold the old system together for another year.

    2. Re: Larger problem by Anonymous Coward · · Score: 0

      We have found out that no one knows the requirements. Our requirements are based on law but law is written so that it doesn't give answers so it has to be interpreted.

  32. Sorry, I had to laugh by lamer01 · · Score: 1

    At the 'better documented' comment. The cool kids say the code is the documentation.

    1. Re:Sorry, I had to laugh by plopez · · Score: 1

      Don't need no stinking' documentation. We're Agile.

      --
      putting the 'B' in LGBTQ+
  33. Nope by Anonymous Coward · · Score: 1

    These are financial services companies. They're not upgrading because there's a huge perceived risk taht the upgrade will fail in a manner that destroys the company. Certainly, the kids believe that COBOL is obsolete and inherently bad, but the existing code base is giving 5 nines of uptime, and new code might fail.

    1. Re:Nope by Anonymous Coward · · Score: 0

      This. Yes there's a thousand ways better to do it, but unlike your smartphone, there can't be any room for error. One mistake can cost billions in financial software. Its not just the cost to create change, but also the cost to validate and then the risk of failure.

    2. Re:Nope by Anonymous Coward · · Score: 0

      This. Yes there's a thousand ways better to do it, but unlike your smartphone, there can't be any room for error. One mistake can cost billions in financial software. Its not just the cost to create change, but also the cost to validate and then the risk of failure.

      Exactly, I was at a chemical plant yesterday and one of the older controls engineers stated "yeah we have some old stuff here, a lot of this technology doesn't advance doesn't advance at the speed of smartphones" to which I remarked "well I wouldn't want a safety system that needs to be rebooted every other day anyhow."

    3. Re:Nope by HiThere · · Score: 1

      The problem is there isn't any significant number of new Cobol programmers. I sure wouldn't want to use it, and I was willing to put up with Fortran II. OTOH, I never really understood Cobol, so take the rest of this post with a large grain of salt.

      I was trying to think what other language might be reasonable to rewrite things in, and couldn't come up with anything. The two that seem closest are Lisp and Ada, and if you have any idea how different those are, it might give you an idea of how poor a fit everything seemed. (And also notice that neither was very popular.)

      My real best guess would be Smalltalk. Another language that isn't wildly popular, and also is having problems with modern developments. (Last I checked there wasn't a concurrent version, and support for unicode was minimal...but that was a couple of years ago.)

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    4. Re:Nope by Pig+Hogger · · Score: 1
      Have you given a thought to PL/1? It has the same data declarations as COBOL, but is a much more structured syntax...

      (Back when I programmed in COBOL, I would label the fist line of procedure “XXXX000” and the last one “XXXX999”, so I would always call a procedure with “PERFORM XXXX000 THROUGH XXXX999”; that was my way of bringing some kind of structure to the COBOL code I was didling with).

    5. Re:Nope by HiThere · · Score: 1

      Actually, I rather liked PL/1. It's a pity that it died rather than improving. It had a lot going for it. And it *was* intended to replace COBOL as well as FORTRAN. It failed at both. Fortran is still going well in specialized areas. In certain ways it's the fastest language beyond assembler. COBOL....well, as I said above, I never really understood it. But PL/1 had more success with Fortran IV programmers than with COBOL programmers, for whatever reason. And the last version of PL/1 that I heard of was a small subset that ran on the z80. That's quite awhile ago. I've heard of new versions of COBOL occasionally since then. So I think PL/1 is as dead as Snobol.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
  34. Clean up your act first by Rick+Schumann · · Score: 1

    How about before you paper-shufflers master the technology you already have, specifically in securing it properly so all our very-much-personal information isn't constantly being stolen, before we give you any new toys to play with? I think I speak for everyone else when I say we're all sick and bloody well tired of companies being irresponsible.

  35. Mainframes by Anonymous Coward · · Score: 0

    I work for an MSP that does mostly small banks, and most programs the banks use for their core business are just GUI frontends for IBM AS400 mainframes. One of the biggest obstacles to "Innovation" is Internet Explorer. The federal reserve websites where you actually send wires and cash orders all still require IE, and compatibility modes for the newer versions. A bunch of programs require Java and/or flash. The vendors are starting to support windows 10, but there are issues. A big issue is for that for regulatory reasons we can't just buy into the Microsoft cloud, or any other cloud service without some serious vetting. So we can push out windows 10, but we have to block onedrive, office online, and every other "innovation" that Microsoft wants to bundle with their OS. Microsoft has the LTSB which actually sounds really good, but they say it's not meant for office drones. Small banks balk at paying twice as much for windows to get the enterprise version, which is really what the pro version should be. Windows 10 Pro is anything but, with ads and GAMES all over the place on a clean install.

    If we had all web apps that don't require windows, then windows most definitely wouldn't be the right tool for this kind of environment. But of course, these web apps wouldn't be as reliable as the time tested IBM Mainframe for actual data storage and such.

  36. I just want to say one word to you. Just one word by Lucas123 · · Score: 0

    Benjamin: Yes, sir.

    Mr. McGuire: Are you listening?

    Benjamin: Yes, I am.

    Mr. McGuire: Blockchain

    Benjamin: Exactly how do you mean?

    Mr. McGuire: There's a great future in Blockchain. Think about it. Will you think about it?

  37. Existing tech, how would they know? by FictionPimp · · Score: 2

    How would they know. I still can't find a bank using proper MFA, good password rules, a solid web and mobile app UI, etc. Most of them are stuck in 2005 or 1998!

    1. Re:Existing tech, how would they know? by Kozar_The_Malignant · · Score: 1

      Nothing like a financial institution's website that requires Flash to inspire confidence.

      --
      Some mornings it's hardly worth chewing through the restraints to get out of bed.
    2. Re:Existing tech, how would they know? by Anonymous Coward · · Score: 0

      A lot of banks rely on cookies and IP address fingerprints as a type of "second factor" authentication. I hit this every time I open up a browser in private mode to do online banking: "We don't recognize you! Please answer your security question, or we can send you a text message..." With consumer banking the problem is with the customers who struggle with the technology, they don't understand that security requires both sides to behave properly.

      And no, I don't use private mode thinking it will prevent my ISP from watching my activity. I use it so I can close the window afterwards and not have session data lingering in my browser for third party sites to exploit.

    3. Re:Existing tech, how would they know? by Anonymous Coward · · Score: 0

      I still can't find a bank using proper MFA, good password rules, a solid web and mobile app UI, etc.

      Agreed. Something at the level of a bank should not be using tradesmen such as UX designers. I expect sophisticated art direction from my financial institutions in their digital architecture just as I would for the physical architecture of their branch offices.

  38. What's holding back innovation? by najajomo · · Score: 2

    "according to a new survey .. almost 51 percent say existing technology is holding back innovation. "

    How about they stop relying on the industry standard Microsoft Windows.
    --

    I'll bet you're the kind of guy that hangs round Reddit fapping off over pictures of furries and yellow-scaled wingless dragonkin

  39. PASS by fluffernutter · · Score: 1

    Why does everyone give business a 'pass' when they complain about something? If this situation is not their own fault, after years of cheaping out on IT, making it a poor career choice, etc then who's fault is it? Furthermore, who the heck are they complaining to that they feel will have more power to change this then themselves? Why do they choose some arbitrary cap for salaries that is below what the market dictates? Why does nobody put up a mirror?

    --
    Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
    1. Re:PASS by plopez · · Score: 1

      Heresy! We must burn fluffernutter!

      --
      putting the 'B' in LGBTQ+
  40. AS/400 != mainframe (it's midrange) by Anonymous Coward · · Score: 0

    AS/400 != mainframe (it's midrange) - I spent a good decade++ programming BOTH directly ON 'em (RPG on their ancestors System 34/36/38 & COBOL on the 400) & then via clientserver GUI frontends (done via Delphi, MSVC++, VB or even Access circa 1994-2008) via clientserver models (via IBM middleware like ClientAccess libs provided @ first (later w/ other methods like ODBC @ first, better lighter methods came later, to DB/2 ISAM-type database structures)).

    All they are, is what PC's in clientserver are for most businesses - ENOUGH to do the job (where a mainframe is overkill for their workload & ability to rent OR purchase - 1 fortune 500 I worked for made that 'mistake' & rented off mainframe time to local universities time-sharing it + HEATING THEIR BUILDING FROM IT (smart engineers imo, lol)).

    * They have 'newer names' for that hardware now (zOS etc. iirc) - but I could care less (glad to be LONG GONE w/ the DAWN & free of it, lol - I am SURPRISED I can recall this much of it in fact, it's been decades) - great 'line of business' hardware - NOT STRICTLY "multitasking" but more QUEUED FAST PROCESSING - it was designed to be though (dedicated boards &/or ASICS all riding on a backplane bled down to PC's SOMEWHAT @ least from them & their mainframe bretheren to make them better).

    APK

    P.S.=> NOT 'busting your balls' - that's just for your future reference (quibbling/semantics? Perhaps, but it's some "FYI" 4U)... apk

  41. Yeah, Times have changed by Anonymous Coward · · Score: 0

    Through the 60's and 70's, blaming "the technology" probably held water. During the 80's, decent technology options (I mean 3rd party, not in-house developed) technology started showing up in many industries.

    Now? Perhaps your internal Political Correctness is showing. You cannot mean "the technology" now. Your corporate politics may hold you back, or leadership, or PMs, or staff availability, or money, or a history of failed projects, or, well a lot of things.

    I'll be kind and suggest that maybe you don't want to shine a light too brightly on your organizational failings. That can be career limiting. However look inside for answers, not at "the technology".

    Change can be scary and big tech projects risky. However if you want to win business from your customers, and they really are demanding new products/services, what are you going to do? Watch your customers move to competitors willing to sell that stuff? Or maybe you ought to fight for that business?

  42. Too hard to change fundamentals by aberglas · · Score: 1

    In complex systems some parts depend upon other parts. So it is very difficult to change those at the bottom without upsetting everything.

    So the solution is to work around the core issues. For example, a web based banking interface does not attempt to store additional information in the ancient COBOL core. Instead, it copies information into its own database, and then syncs via complex protocols. Over time more and more of these work arounds make the system harder and harder to change.

    This is why a small, new bank, with a tiny IT staff and clean, new systems can compete with a large established bank with huge staff. (Plus Parkinson's law of course.)

    1. Re:Too hard to change fundamentals by Anonymous Coward · · Score: 0

      I'm currently in a project where we had old legacy system. The old system is big dependency network where it is nearly impossible to change e.g. database fields because it would affect the whole system. They also have tens of thousands of customer that use their API, but they have no idea how does APIs work or what fields there even is, they have relied completely on their customers to test their external interfaces. The data is heavily corrupted because the old system doesn't work like it should.

      What we did is this:
      - One person investigated the whole system the best he could.
      - Then the person wrote initial POC how you could do the same better, including a complete rewrite of how data is stored. He also made plans of what is the smallest possible change that need to be done so that the changes can be put into production without the need of making massive changes to the current system.
      - Then 2 developers joined the team and improved the POC further, doing performance testing, testing implementation of features and writing POC of conversion software that will convert the data from old model into the new one.
      - After that few new developers joined and later a few more, having a small team in total.

      Summary:
      - Even old, "impossible to change" legacy system can be changed.
      - You only need a small team and a few years to do it, if you need more, you need a better architect.
      - It is not hard to design and write these systems from the scratch, that takes perhaps 10% of the project time, the hard part is keeping the old corrupted data in shape and keep old legacy interfaces to external systems still working after the change, this is hard, because the legacy interfaces had so many bugs. Simulating correctly working system is easy, simulating bugs is hard, but you never know if customers depend on those bugs.

  43. Thanks Team Creimer! by Anonymous Coward · · Score: 0

    Thanks Team Creimer!

    To thank you further, here is the story of creimy the mountain and his royalties. Creimy finally got rich! It should be an inspiration for you and motivate you not to give up!

    Here is the story of creimy the mountain and his royalties!

    This story was inspired by cdreimer, the parent poster. The story was written by a visionary on cdreimer birth date.

    The story of creimy the mountain explained:
    https://en.wikipedia.org/wiki/...

    Creimy is a typical mountain who poses for postcards, living with his wife Ethel, a tree, between the cities of Rosamund and Gorman, California. The main features on his mountainous face are two large caves, resembling eyes, and a cliff for a jaw, which moves up and down when he talks, puffing up dust and boulders.
    click above link to read more, he even destroyed Edwards Air Force Base just by passing by...

    Listen to the audio version here:
    https://www.youtube.com/watch?...

    "Creimy The Mountain"

    includes quotes from Pomp and Circumstance March No. 1 in D major (Edward Elgar), Johnny's Theme (Paul Anka), Off We Go Into The Wild Blue Yonder (Crawford), O Mein Papa (Paul Burkhard), Over The Rainbow (Harburg/Arlen), Star-Spangled Banner (Smith/Key), Suite: Judy Blue Eyes (Stephen Stills)

    One, two, three

    CREIMY the Mountain
    CREIMY the Mountain
    A regular picturesque
    Postcardy mountain
    Residing between lovely
    Rosamond and Gorman
    With his stunning wife ETHELL, A tree! A tree!

    CREIMY was a mountain ETHELL was a tree Growing off of his shoulder

    CREIMY was a mountain
    (CREIMY was a mountain!)
    ETHELL was a tree Growing off of his shoulder
    (ETHELL was a tree growing off of his shoulder)
    (hey, hey hey!)

    Creimy had two big
    Caves for eyes,
    With a cliff for a jaw
    That would go up 'n down,
    And whenever it did,
    He'd puff out some dust,
    And hack up a boulder (HACK!) Hack up a boulder (HACK! HACK!)
    Hack up a boulder (HACK! HACK! HACK!) Up a boulder

    Now, one day, now I believe it was on a Tuesday, a man in a checkered double-knit suit drove up in a large El Dorado Cadillac, leased from BOB SPREEN

    ("Where the freeways meet in Downey!")

    And he laid a HUGE, BULGING ENVELOPE right at the corner of CREIMY THE MOUNTAIN, that was right where his 'foot' was supposed to be.

    Now, CREIMY THE MOUNTAIN, he couldn't believe it! All those postcards he'd posed for, for ALL OF THOSE YEARS, and finally, now, AT LAST, his Royalties!

    Royalties! Royalties Royalties! Royalty check is in, honey!

    Yes, CREIMY THE MOUNTAIN was RICH! Yes, and his eyeball-caves, they widened in amazement, and his jaw (which was a cliff), well it dropped thirty feet!

    A bunch of dust puffed out! Rocks and boulders hacked up, (hack! hack!) crushing 'The LINCOLN'!

    I gave him the money He acted real funny He hocked up a rock and It TOTALLED my car!

    Oh, do you Know any trucks Might be bound for THE VALLEY?
    I don't wanna stand here All night in this bar (Dear Lord)

    I don't wanna stand here All night in this bar (No shit!)

    I don't wanna stand here All night in this bar!

    By two o'clock, when the bars are already closed down, CREIMY had broken 'THE BIG NEWS' to ETHELL. And with dust and boulders everywhere, CREIMY, choked with excitement, announced

    "ETHELL, we're going on a VACATION!"

    Yes, and they WERE going on a vacation! (Oh, and ETHELL, ETHELL, ETHELL, like every little woman, she of course was very excited! She creaked a little bit, and some old birds flew off of her.) CREIMY told ETHELL they were going to Yes! They were going to NEW YORK!

    "ETHELL, we're going to New York!"

    But first they were gonna stop in LAS VEGAS

    It's off to LAS VEGAS to check out the lounges Pull a few handles,
    And drink a few beers, (Oh, ETHELL!)

    ETHELL, my

    1. Re: Thanks Team Creimer! by Anonymous Coward · · Score: 0

      Douche

  44. Consumers want.... by HiThere · · Score: 1

    The foolish consumers may want "better, faster financial products.", but that's nearly a contradiction, and is one if better includes more secure.

    FWIW, I don't want my financial data going over the internet in any way. Well, I can't stop that, but I can restrict the amount of exposure I give myself. You'd think nobody had ever heard of Spectre or Meltdown. I've given up all purchases over the internet until those are widely patched. And I've never been willing to do on-line banking, despite the ads promoting it.

    P.S.: To the extent that a "financial service" thinks of me as a consumer rather than a customer, I'd rather not do ANY business with them.

    --

    I think we've pushed this "anyone can grow up to be president" thing too far.
  45. 50% of businesses are below average by Anonymous Coward · · Score: 0

    news at 11

  46. No Continuing Education by Anonymous Coward · · Score: 0

    The financial firms gave lip service to educating their employees while relentlessly replacing them with cheaper employees, fresh out of college.

    Unemployed and without income, the former employees gradually grew less relevant and, with rising housing prices, they were quickly driven out of the metro areas where they were in the most demand.

    Over and over, financial firms did this, driving the bar lower and lower.

    Now, they complain that they cannot find good, sharp, experienced people.

    I save, go fuck yourselves, assholes.

  47. Alternate Title: by stolidobserver · · Score: 1

    51 Percent of Financial Services Companies Believe that Non-Existent Tech Can Help Them

  48. Re:So they made a conscious decision not to upgrad by Agripa · · Score: 1

    Unless those who have the technical skills start retiring. (think: COBOL)

    Unless those who have the technical skills were downsized.