15 votes

An oral history of Bank Python

2 comments

  1. unkz
    Link
    I once hired a developer from one of the “big six” national banks (those in the know will instantly know which one), and it was a weird experience. They obviously knew how to program, but only...

    I once hired a developer from one of the “big six” national banks (those in the know will instantly know which one), and it was a weird experience.

    They obviously knew how to program, but only knew the core language. They didn’t know anything about the larger ecosystem. At the bank, it was a huge ordeal to get an external package approved so they had shitty in house versions of everything regular developers would use. That meant they had a surprising amount of technical knowledge of things you would not normally need to know, but were quite inefficient at getting things done for a long time until they got up to speed on working in a less controlling environment.

    6 votes
  2. misk
    Link
    Hah, I've seen "Minerva". This story explains some things like how quickly external data ingests could be reconfigured. I also recall that it was still Python 2 and some internal materials cited...

    Hah, I've seen "Minerva". This story explains some things like how quickly external data ingests could be reconfigured. I also recall that it was still Python 2 and some internal materials cited that it could possibly be the biggest Python app in existence.

    Internal banking apps can get whacky sometimes. In another bank I worked with an app for FX and rates valuation that had internal logic so bizzare it took months for people to understand and some probably never did.

    5 votes