Blog

Some may ask: what is the point in doing code review if we have automated tests? Let me ask differently…what exactly do tests test? Is the app correct? Or whether the app has errors? My answer is: tests can only help us know if the app has errors. Tests alone, don’t care about the quality of the code.

As software developers, we write code which falls into one of two categories. The first one is the business logic code – the essence of the software we create. The second one is infrastructure code – a backbone of the application. Did you ever think what is the optimal ratio between an amount of code in these two categories? In this article, I will share my observations on this topic. Small side note, in the course of this article I will use term BICR to denote Business/Infrastructure Code Ratio.

It would seem that a good choice of technology is the basis of a good project. It would also seem to be a simple choice. Nothing could be more wrong. Read on to see how you can go wrong and suffer from unnecessary costs through a lack of a proper and accurate analysis of business assumptions and MVP.

Stefan Moritz, a well-known service design coach, said: „80% of companies believe they deliver outstanding value and a superior customer experience, but only 8% of their customers agree.” Let’s find out how to be a part of that 8% group. Regardless of the role, we play in a project.