Sundeep Gupta

Understanding why products are built the way they are is crucial for engineers looking to evolve them. The moment this understanding erodes, development stalls, time is wasted, and products break. At Connected, we have taken the first step to solving the problem: naming it.

This post explores Swift’s Never via two real-world examples. It illustrates how we can write impossible to execute code — expressed via types. This reduces our need to use fatalError, and // This should never happen comments. Writing expressive, clean code is important for building quality products that are maintainable. Moreover — it feels good!

My team and I recently discovered a bug in one of our projects, and the culprit turned out to be the FlatMap operator—or rather, our misuse of it.