6 ms·
> When TSB split from Lloyds Banking Group (LBG), a move forced by the EU as a condition of its taxpayer bailout in 2008, a clone of the original group’s comput
by lordnacho 9y ago
> When TSB split from Lloyds Banking Group (LBG), a move forced by the EU as a condition of its taxpayer bailout in 2008, a clone of the original group’s computer system was created and rented to TSB for £100m a year.
> That banking system was a “bodge of many old systems for TSB, BOS, Halifax, Cheltenham and Gloucester and others” that had resulted from the “nightmare” integration of HBOS with Lloyds as a result of the banking crisis, according to one insider who had extensive access to and intimate knowledge of LBG and TSB’s internal systems over a prolonged period.
That sounds completely crazy. If you've got £100m a year in IT budget, why on earth would you buy a clone of Frankenstein?
You could hire a fine team of devs to build you a modern system. Then again, I'm not the kind of guy who believes in "never rewrite" which seems to be the advice.
> On Thursday he admitted the bank was on its knees, announced that he was personally seizing control of the attempts to fix the problem from his Spanish masters, and had hired a team from IBM to do the job.
This doesn't give me much confidence, either. Hiring outside help is a Coase problem. You're going to find frictions dealing with the externals. And it will cost you, I'm guessing, at least £100M a year.
With that kind of budget, and with IT being more or less all a retail bank does, you should hire hundreds of experienced staff, make them integral to the business, and let them solve the issues as they appear to the business units. When things happen they will have an idea of what the priorities are. There are plenty of software people who understand how banking works, and what systems are needed. Go and hire them.
- roel_v 9y agoYou can't just say 'hey guys we'll build you a new system, see you in two years'. It's about the migration path, it always is, building new systems is easy.
- collyw 9y agoThats the difficult part. Then you have an untested (in the wild) system.
- pebers 9y agoThat was the system they already had, spinning out a clone of the old one they were using was presumably seen as the easiest way to separate the two banks. And for all the negative press it got in that article, it did at least work...
- Stranger43 9y agoAnd shut down your entire operation while said team worked? The problem is that the average banks system is a kind of Frankenstein tree that have grown inside and around every policy, procedure and task the bank performs without any coherent design and with several dozen loosely coupled component each with is own poor and fragmented documentation. And while it's typically only required to remain up 16-18 hours a day you have a zero allowance for unplanned downtime and a fairly high peak load which along with the age and complexity of some of the components make the entire systems a nightmare to run on a tight budget. And it's worth nothing that the system that failed was not the Frankenstein system they inherited from Lloyds but the new one they tried to import from Spain.
- walshemj 9y agoWhich is based on a cobol system from Accenture from what I hear.
- ethbro 9y agoThis. Banks can't have extended downtime. So if a $100M budget would get a new system built, then what they would need is a $200M budget ($100M to run legacy in prod + $100M to build new system and gradually migrate). The only good in-house systems I've ever seen we're (a) based on vendor reference designs w/ minimal changes, (b) based on OSS, (c) architected by some very smart people who stay at the company for non-monetary reasons. Because when you boil it down to it, no company is big enough to solve a problem better than a group working with multiple companies (unless the problem is trivial). Or to word it another way, are you bigger / better / smarter than both of your top competitors put together? If no, then don't reinvent the wheel.
- Khaine 9y agoBanks can't have any downtime. They need to be able to process EFTPOS and Credit Card Transactions 24x7. Now, not all systems need to be always available in the bank, but the key ones do.
- Chyzwar 9y agoI worked in two big banks. It is not easy. Many regulations and existing legacy systems result in systems build around FTP and flat files. Bussiness side also does not have a clue, sometimes it is very difficult to tell why someone made a decision 10 years ago since nothing is documented. The only hope is to replace systems one by one and make gradual migrations. Problem with this approach is that you need to add new interfaces to existing legacy systems and add some crazy stuff to the new system. Above would be possible if you can hire top talent and retain it for many years. With current IT market, it is not possible. Even google and facebook that pay way above market struggle to retain people for more than two years. Additionally, business domain is boring and technology is outdated.
- jstanley 9y ago> Even google and facebook that pay way above market struggle to retain people for more than two years Perhaps they're not paying "way above market" then. If buyers paying "way above market" struggle to attract sellers, it means the buyers are wrong about what the market price is.
- user5994461 9y agoPeople find a partner, have children, move to follow their partners or move back to take care of their parents. Projects are completed, roles shift, company changes. A higher salary doesn't have any effect on any of the above.
- Chyzwar 9y agohttp://uk.businessinsider.com/employee-retention-rate-top-tech-companies-2017-8 http://uk.businessinsider.com/comparably-50-best-paying-big-companies-salary-employees-2017-11 Talented people want to make an impact. Working for google building proto-to-proto services is opposite of making an impact. On average your work will have very little spotlight but you will make lots of money for the company.
- Finnucane 9y agoIf you were a jazz musician in the 1920s, the best-paying stable job you could get was in Paul Whiteman's band. So Whiteman was able to attract some of the best players of his day (well, the best white players of his day, anyway). But the work frequently meant playing boring arrangements for upper-class toffs. There was a fair bit of turnover in the staff despite the good pay. Some of his players just drank themselves into an early grave.
- user5994461 9y ago>>> That sounds completely crazy. If you've got £100m a year in IT budget, why on earth would you buy a clone of Frankenstein? It's a fairly low budget for a big company. That's a few hundreds employees at an average cost of $100k then the rest goes to hardware, suppliers, support contracts and other costs.