Systems Switchover: Chase Absorbs WaMu

Washington Mutual customers gird themselves for final transition to Chase

2 min read

[corrected on June 26, 2009]


I've been dreading this day ever since Chase took over Washington Mutual last fall in the midst of Great Meltdown. What has me wondering if I'm going to wake up on July 26 to my own personal ecomomic hell was summed up nicely by last October:

Online banking, user names and passwords will also stay as is. Direct deposits, automated payments and transfers should continue uninterrupted.

I like the optimism of the phrase "should continue uninterrupted." In fact, this whole process has been filled with nothing but sunny prognostications of Chase IT department triumph and promises of a smooth transition. Fear not, customer, you won't lose access to your money. Your bills will continue to be paid. And if you're as fortunate as I am to be paid via direct deposit on the very day the transition happens, don't sweat it.

Well, I'm sweatin' it. In fact, I'm surprised there hasn't been a run on deposits at least as substantial as the one that happened to the tune of $16.7 billion last September when it looked certain that WaMu was going to go down as the biggest bank failure in U.S. history.

Think about it. Millions of transactions will have to be managed by a new system at the proverbial flick of a switch. Not that banks don't do this all the time--they do. Heck, WaMu itself absorbed 29 financial institutions between 1990 and 2006. But--and Risk Factor readers, please correct me if I'm wrong--nothing on this scale has ever been attempted between two commercial banks.

So stay tuned. And if on July 26 you hear hundreds of thousands of people cursing like sailors at computers, ATMs, and swipe pads, you'll know that a monumental failure is upon us. If, on the other hand, all goes smoothly, someone needs to buy those Chase programmers a few bottles of bubbly.


The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
A plate of spaghetti made from code
Shira Inbar

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less