[HN Gopher] Python toolkit for quantitative finance
       ___________________________________________________________________
        
       Python toolkit for quantitative finance
        
       Author : tzury
       Score  : 99 points
       Date   : 2024-06-29 17:07 UTC (5 hours ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | raluk wrote:
       | In readme, they should write tutorial on how to make money with
       | this. I mean is there any other reson for using this software?
        
         | nurettin wrote:
         | To make money, write software for people who will make money.
        
         | constantcrying wrote:
         | >In readme, they should write tutorial on how to make money
         | with this.
         | 
         |  _You_ don 't make money with this.
        
       | NewsaHackO wrote:
       | This seems pretty basic, really just classes of common data
       | structures used in finance. Closer to what you would expect for a
       | final project for a undergrad in OOP course.
        
       | kingkongjaffa wrote:
       | The only utility here is to study the design.
       | 
       | Access to anything useful is behind GS specific data APIs via
       | https://developer.gs.com/docs/gsquant/authentication/gs-sess...
        
       | scrlk wrote:
       | Does GS still use their proprietary Slang language or has that
       | been phased out in favour of Python?
        
         | 1htfp wrote:
         | Still very much present, it powers "SecDB" (which is pretty
         | much the nervous system of the entire markets business). While
         | there's certainly been openness to Python/etc and tech to
         | integrate Slang into the 21st century, it's the kind of thing
         | that's hard to imagine ever being phased out.
        
           | simonh wrote:
           | I worked at Bank Of America for a while on the Quartz
           | platform, which is their Python based clone of SecDB. The
           | lead architect was one of the founders of the Slang/SecDB
           | platform at Goldman. It as great fun to work on. Incredible
           | power at your fingertips.
        
       | CoderJoshDK wrote:
       | This code commits so many sins. The contributing standards are so
       | strange. And what is up with the licensing?
       | 
       | Looking at this code hurts my eyes.
        
       | conformist wrote:
       | This is bizarre over engineering:
       | 
       | https://github.com/goldmansachs/gs-quant/blob/51a7ff1afb722c...
        
         | heyoni wrote:
         | The pointless act of "encapsulating" nothing? I see that a lot
         | unfortunately =[
        
           | IshKebab wrote:
           | Presumably @plot_function does something. Also there are lots
           | of other functions in the same API that are more than one
           | line.
           | 
           | I suspect he wouldn't have thought it was over engineering if
           | it didn't have such a long comment for one line of code...
           | Which is silly.
        
         | nixpulvis wrote:
         | What about the @plot_function bit? Also, wrapping dependency
         | calls for a more consistent interface isn't necessarily a bad
         | thing.
        
         | sk11001 wrote:
         | Does someone have LOC as a performance indicator?
        
           | ng12 wrote:
           | Unironically probably. The only place I've ever worked that
           | used LoC as a performance indicator was a hedge fund.
        
       | richardw wrote:
       | Rather than just dump on it, I'd find it more interesting to hear
       | how it came to be and what it's used for internally (if so).
       | 
       | I've seen surprising stuff that had rational reasons under closer
       | investigation. Companies have cultures and internal priorities
       | that make sense when you're inside the bubble, but look weird
       | from outside.
        
       | data_ders wrote:
       | Cool to see some "bank Python" that Cal Paterson had described
       | previously is now open source https://calpaterson.com/bank-
       | python.html
        
         | snovymgodym wrote:
         | Nah this looks pretty orthogonal to that. This just looks like
         | a collection of pure python libraries for doing common quant
         | work. The thing Cal Peterson is describing (which is pretty
         | transparently JP Morgan's Athena) would be SecDB at Goldman and
         | would be running on their proprietary scripting language called
         | "Slang". None of that is open source.
         | 
         | Goldman was the first place to do a system like that, and when
         | it was copied at other investment banks like JP Morgan and Bank
         | of America, they opted to use Python instead of an in-house
         | language and so "bank python" was born. Actually, the banks all
         | poached engineers from one another, so many of the people that
         | built the system at one place ended up building it again at
         | another, hence why there are so many similarities between the
         | equivalent systems at all these US investment banks. Some of
         | those people eventually went on to build it again as a SaaS
         | offering: https://www.beacon.io/
        
       | caseyf7 wrote:
       | The toolkit may be free, but the data is very expensive.
        
       ___________________________________________________________________
       (page generated 2024-06-29 23:00 UTC)