Photo by Alice Pasqual on Unsplash

The deepest dive yet!

Oh my — the SOLID! Over the course of 2019 I have led 20 interviews with iOS developers, and I never hesitated to fire the question of “Alright, let’s talk about the SOLID, tell us, what is it about?”. And over the past 2 years I have myself been interviewed 15 times and the very same topic has unsurprisingly resurfaced consistently.

The comedy of this seemingly bureaucratic procedure is that everyone, who is prepared to rapidly spew details on what’s SOLID about, has a 50% chance of knowing some aspect or a compelling example reinforcing any…


I clapped 50 times even though I didn’t even read the article because of the paywall.


Thanks to undraw.co for a great illustration

This article focuses on different limitations of the Reactive Extensions implementation of FRP paradigm.

Reactive Extensions is a family of frameworks that allow for functionally-reactive programming in imperative programming languages. One of the greatest factors that allow us to treat all of the implementations as a part of one family is the fact that all of them bring identical concepts to the table, which is reflected in similar primitives naming, operators semantics and life-cycle control tools. The advantages of x for commercial projects include:

  1. Seamless asynchronicity
  2. Transformation atomicity
  3. Use-case configurability

Right now we will, however, take a tour on 3…


Thanks to undraw.co for a great illustration

In this article, I would like to discuss the concept of an adventurous and thoughtful error handling in a modern iOS application.

The concept consists of two major aspects:

  1. Building error trees
  2. Producing the user-friendly error state visualization lazily

All the code presented in this article can be found and fiddled around with here.

Error tree is a compound data structure that is designed to make it easy to see what exactly is the reason behind a failure of a complex operation.

— literally me, writing this very article.

The main premise here is to treat your error objects as…


Photo by Vashishtha Jogi on Unsplash

The future is very promising and here are my primary reasons:

  • ReactiveX has lost the debate on `Error` event type generic specification
  • Expect less mudball mish-mash architecture-less cancer-code in the Darwin application programming.
  • MVC family of architectural approaches is to die out in GUI programming being inferior to FLUX.

ReactiveX has lost the observables error type debate

In the Apple programming world there has been a debate. Should the reactive programming framework propagate errors as:

  • A most common generic Exception-like type
  • Strong well defined as deep as possible type defined by the programmer

And there you go: `ReactiveCocoa` being at times more or less popular did the second…


“mountains under cloudy sky” by Leo SERRAT on Unsplash

Swift is a great language to write applications in. However, being more or less proficient in numerous other programming platforms, one will of course acknowledge that one of the most flexible and truly powerful programming languages out there is ECMAScript. In this article I am going to talk about such a syntactic construct as the anonymous class. Consider this little gist.

This one is not the class in its entirety, but just the dynamic behavior I would occasionally end up looking for while working on a project. …


Me and my wife are both web developers. In fact we’ve started dating while doing a project together. I guess you could say that we MERGED WITHOUT CONFLICTS.

iOS. Doing something with my life. Good food and good time.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store