Michal Zygar

Every now and then when working on the new features, our app crashes. Easy, peasy, right? Happens all the time. However sometimes all you can see is: libc++abi.dylib: terminating with uncaught exception of type NSException and then you wonder: Where did the stack trace go? The error message is not really helpful and asking lldb for more info using expr $arg1 does not work. It may cause you to be stuck for a couple of hours, trying to pinpoint the cause of the exception. »

Sometime ago I’ve had a great discussion with Danny Ruchtie about the AB Experimenting on features. Iterative design It uses grand design as a direction we’d like the project to go. However, the changes are introduced iteratively. Each change introduced is atomic. You get a clear picture whether it is improving KPIs or not. If not, you tweak it until you get a positive result. Then test next atomic feature on top of it. »

Hello world This is my first post. So blah blah blah. Long live and prosper. //Photo by Adam Solomon on Unsplash »