There’s a concept of “best practices across industry”, as I experienced in Macq. Using new technology, things can be done faster, at a large scale, and more automated, even though I may feel it doesn’t make such a difference.
CTO’s don’t want to be seen as laggards. Same motivation at MS-Iceman, Quoine …
- PWM-billing, PWM-comm. I remember Mark wanted “strategic improvement” not incremental improvement. He needs it for his promotion 政绩
- RTS infrastructure was considered (by Jack He and outsiders) outdated and lagging behind competitors
You can call it “ruthless march of technology” — a ruthless progress. At a fundamental level, this “progress” can wipe out the promised benefit of “slow-changing, stable domain knowledge”
- quant skillset
- SQL skillset — affected by noSQL
- c++ skillset — perhaps affected by c++0x
- FIX skillset — perhaps affected by faster proprietary exchange APIs?
- … However, the skills above are still relatively robust. Other skillsets (they are not today’s focus) have proved arguably more robust against this march — sockets, pthread, STL, coreJava, bond math,.. I listed them in my spreadsheet pastTechBet.xlsx.