I would outline 3 areas: 1) Modeling capacity/latency of complex system with queuing theory (basically creating spreadsheets that can 'calculate' how much serv

I would outline 3 areas: 1) Modeling capacity/latency of complex system with queuing theory (basically creating spreadsheets that can 'calculate' how much servers you need with what I/O throughput/etc for our software) 2) When looking at tables in data-warehouse, as 'types' -- I felt I could benefit from leveraging modern type theory, where I could at least categorize schemas (filds/relations) into 'Automatically-transformable into target warehouse schema' vs 'human intervention is needed'. Besides natural complexity, the papers in type theory use that fraction notation :-). For some reason difficult for me. 3) Various data de-anonymization proofing techniques, differential crypto, and tamper-proof logging. Ability to read financial mathematics and NLP technique is something I do not need now, but I would have benefitted significantly in my past.