The o2 used a unified memory scheme so it's graphics were never as fast as it's big brother the octane's impact graphics but because of the unified memory it was a texture power house in comparison, close to a GB of texture memory in 1996 is mind blowing, in comparison the ocatane's impact graphics had 4 mb of texture memory and if you payed out the big bucks for a max impact with double the memory(which was the size of a large motherboard)... you still only got 4mb because the extra memory was basicly sli. and a graphics board that had the reputation of desoldering it's own memory off.
In 2000, I was the 20th-or-so full-time engineer at VMware, where I worked for 9 years. Then was at Facebook from 2009 to 2016, where I worked on the search backend (now replaced), HHVM (which still runs the Big Blue Application, a shrinking portion of the Meta Empire), and started FAIR in 2015 (which finally seems to have turned around the "open" sign with Yann's departure).
In 2016 I started at Slack as Chief Architect, where I mostly did not write a ton of code. I worked on a job queue scheduler which I would not be surprised to find has been replaced. And after that I was mostly encouraging/advising people doing Real Work.
All of which is to say, it is quite possible that the last code I've worked on professionally that is out there running on customer machines ... is that libpthread mutex bug fix from when I was barely old enough to drink.
A 3dfx card running in an O2 surely deserves a similar moniker :)