Why you should use MVVM instead of MVC

The View-Controller in MVC is responsible of interpreting the Model (business logic) and managing UI. See that "and" in the middle ? It's a sign that a class might be breaking the Single Responsibility Principle.  In theory, MVC sounds pretty nice, in practice it usually ends up the same:...

Cross Cutting Concerns

A programmer writes code to query his database. He uses the log function over and over again. Then you get to the UI and use the same logger. You end up with using the same class cross cutting through all of your app modules. You can think of many concerns that'll cut your app like caching, analytics,...

CoreLocation limitations - how to overcome them ?

Let's say you have 100 items at your small store and you want to get notified in background every time you're in a proximity of each on an iOS app. The answer seems easy, right ? Let's use iBeacons! After some time you finally get to the final conclusion: iBeacons are useless for your shop. CoreLocation sucks  Don't get me wrong, CoreLocation is a very good high level library but it's limitations...

Drawing clear lines in software architecture

While reading the web I've stumbled upon an interesting article "Reusable Software? Just Don't Write Generic Code" that instructed: "Do not introduce an abstraction layer unless it is clear that you will have multiple implementations (YAGNI principle)."This comes on strong for one important reason: it explicitly tells you not to do something, which in my opinion needs strong...