Behind the trading screens, big banks run sprawling in-house platforms — the "Bank Python" phenomenon — where a single internal framework, a global object database, and decades of accreted business logic power enormous amounts of money movement.
The oral history resurfacing now is fascinating because it inverts the usual tech narrative. There's no clean architecture, no open-source glory, no conference talks. There's a closed, idiosyncratic system that a small priesthood understands and that absolutely cannot go down.
Why it matters
It's a useful corrective to the idea that important software looks like what's trending on GitHub. Some of the most consequential systems on earth are deliberately invisible, optimized for one institution's reality. For engineers, it's also a sobering preview of where today's "move fast" codebases drift after twenty years of nobody being allowed to rewrite them.
Trending on calpaterson.com — analysis by GenZTech.