For the past month, Tristan has been battling with JPMorgan's third party vendor, ION, with a problem no one seems to be able to find. After ION continued to deny their part in the problem, Tristan had to repeatedly defend his team and point out ION's own errors. Then he had to hold a meting to demonstrate the error so they can try and come to a solution. After all that, they still couldn't figure out what was causing the error, so now Tristan just has to build safeguards into his code to prevent the problem that they can't "technically" fix.
On a more exciting note, he has created a really cool new tool for his common software code that will be very useful and can be used across all of their projects. He's very proud of this, and so am I (even though I don't *entirely* know what it all means). ;)