Most tech blogs focus on solving difficult problems, or learning lessons from the unexpected, like outages. This post, however, is about foresight. Software engineers often don’t have time for foresight—they’re always building the next thing in the Product pipeline that will make more money/time/happiness, leaving little time to pursue forward-thinking endeavors that at first glance might not contribute to the bottom line. Here at the Rubicon Project, however, we’re allowed to roam free every so often to see what crazy hare-brained scheme we can come up with.
One of these schemes wound up paying dividends thousands of times over, and is now a deeply ingrained, mission-critical portion of our entire technological stack.