Where the Inverse staff talks about the future of media and tech.

At Inverse, we obsess over one question: What could happen next? To provide answers — and there are many — we search out emerging ideas, new technologies, and simmering trends as well as fearless innovators, designers, and thinkers. We’re compulsively curious not only because we’re fans of progress, but also because we want a glimpse of the future and the chance to better plan for and enjoy tomorrow.

We prioritize Service Oriented Architecture principles at Inverse. That means we have small, maintainable components with clearly defined responsibilities. They communicate with one another (mostly), via Representational State Transfer, or REST, APIs.

This provides flexibility and has served us well with the exception of one significant facet: Testing. When testing, one should avoid:

  • Dependence on external services running on the same machine.
  • Slow tests.

Because applications inherently rely on external services, it is critical to have a testing strategy in place for those dependencies.

We recently started using Bypass and I will explain how we arrived there and specifically how we are using it.

What Is Inverse?

Scroll through our publication and you’ll find stories about neurology research next to criticism of Fetty Wap and reports into the future of genetically modified pumpkins. The topics we cover run the gamut, but our approach does not. We treat the events of the present as evidence we can use to form a not at all unified vision of the future. Our writers use our three verticals — entertainment, science+tech, and life+work — to chase the topics that interest them down a rabbit hole.

We take a scientific approach to analyzing culture and a cultural approach to talking about science. Since our launch in early August, we’ve endeavored to analyze the world thoroughly — if not consistently. Our aim is to better understand tomorrow by examining today. And if you’re into that sort of broad statement, you can check out our mission statement here.

I’ve been obsessed with the future since I was a little kid.

Imprinted with images of an advanced world from the sci-fi movies, books, and comics I devoured from an early age, I wasn’t content to get to the future the old fashioned way — by waiting.

To speed up the process, I built myself a time machine out of cardboard boxes and spare wires. It didn’t work (my calculations for the flux capacitor must have been off), but I have, in a sense, been working on that same project ever since.

Fast forward to 2015, and I’ve joined with some phenomenally smart, forward-looking people to launch Inverse, a publication obsessed with the future and hell-bent on accelerating, critiquing, and celebrating its arrival.