Future of Coding is an online community with a welcoming, cooperative, and revolutionary spirit. We are unified in the belief that the common practice of programming is tragically less humane than it could be.

Future of Coding

I was a core contributor for many years on <https://github.com/ReactiveX/RxJava|RxJava> 1 &amp; 2. My largest impact was to identify and pushing Erik Meijer and Ben Christensen to incorporate back pressure in to RxJava 2 which influenced <http://www.reactive-streams.org/|reactive streams> and eventually <https://docs.oracle.com/javase/9/docs/api/java/util/concurrent/Flow.html|JDK 9+ Flow>.

One of the ways `Observable` are defined is as the dual of `Iterable`.
```Iterable -&gt; Observable
calling iter.next() -&gt; having onNext() called
throwing an error from iter.hasNext() -&gt; having onError() called
hasNext() returning false -&gt; having onComplete() called```

the insight on reactive or async programming is the dual of debugging. With synchronous paradigms it is `When something goes wrong a bad thing happens` but for all reactive paradigms the dual is `When something goes wrong a good thing doesn't happen`