I wish I could find it--I think it was on the Uber engineering blog--but I remember reading a post in which they talked about choosing a less "optimal"/"efficie

I wish I could find it--I think it was on the Uber engineering blog--but I remember reading a post in which they talked about choosing a less "optimal"/"efficient" implementation in order to better cater to the available hiring pool: it's cheaper and easier to throw more money at hardware, than conjure up the necessary engineering talent That resonated with me as I turned back around and gazed at the elegant, efficient, and inscrutable-and-difficult-to-debug Reactive-Extensions-based backend I was working on. Maybe Task<List<T>> would have been "better" after all