In this post, I’m going to talk about git bisect and how it helps finding buggy commits or those who don’t meet some kind of requirement. By using it, git will suggest commits where a breaking change might be introduced. Let’s see how we can use it.
Microservice architectures are here to stay and, when implement them, we need to face some troubles we don’t suffer in monolithic systems. How to fetch and aggregate data from several services to serve a single request is one of them, and API Gateway pattern is what we need to solve it.
A linear recurrence problem means a problem that can be represented as a function such that each term is a linear combination of the previous ones. A classical example is Fibonnaci’s:
After more than 3 years working as backend (and mobile) programmer mostly in the Java Virtual Machine ecosystem, I have realized that no one of those procedural MVC/MVP/MVVM patterns have made me feel confortable when implementing new features or big changes in a project. Also, ER-ending classes (Controller, Manager, Helper…), that are well accepted and used in many frameworks, don’t help with that either: they will get bigger and bigger and you will have to segregate them without any logical criteria. And when that happens, you’re screwed. Maintainability becomes really hard.