Banking software more often than not is the epitome of software held together by duct tape. It's a jumble of obsolete systems communicating via convoluted and opaque protocols.

Think COBOL, mainframes, huge, cumbersome application servers and database systems.

It's just that banks have enough money to throw at problems that arise with these systems.

well then, i guess youre right.

> crud web app shop

CRUD != crud

I don't know if you are making this error, but I it all the time on /r/cscareersquestions and it is a foolish conflation.

crud: crappily-built product

CRUD: a set of UI operations on records in your data model.

You can totally have a well-built CRUD app maintained by a team that cares about code quality.

Yes, but CRUD applications are typically done for small applications on uninteresting problems where people don't really care about code quality. So they have a bad reputation.

The worst CRUD applications, is where they've been extended where they are no longer CRUD but the architecture still assumes CRUD.

maybe i just dont care

maybe it was intentionally conflated to call CRUD usually crappily-built

maybe i dont subscribe to your nomenclature

maybe you can have well-built crud apps (omg I did it again and this time its an oxymoron), but if you pick out a crud app at random, I'll give you 10:1 odds that its code quality is absolute garbage

Alternatively,if we're being pedantic, we can go to the original definition, Chalk River Unidentified Deposit (later determined to be activated corrosion products.)

This seems to be a backronym, rather than the word's actual etymology [1].

[1]: https://public-blog.nrc-gateway.gov/2015/03/31/crud-another-...