Are Stubs and Mocks Harmful?

5 minute read

I stumbled upon this video, and boy it is so amazing! (if you ignore the annoying audience asking non-stop some annoying questions). This is clearly one of the most inspiring videos I have ever watched. So I must take some notes down and spread the idea as well. I deeply believe that it is actually easy to make things complicated, on the contrary, it is hard to make things simple and elegant.

Coffee Maker - An OOD case study

3 minute read

One of uncle bob’s videos talks about how to design a coffee maker, I think he nailed it. The problem is to implement a software component that controls a coffee maker. Requirement The Mark IV Special makes up to 12 cups of coffee at a time. The user places a filter in the filter holder, fills the filter with coffee grounds, and slides the filter holder into its receptacle. The user then pours up to 12 cups of water into the water strainer and presses the Brew button.

Use Interface Segregation Principle to Implement an Android Logger

1 minute read

Recently at work we has been talking about implementing some kind of Analytic interface for all the analytic libraries we are using, like Localytics and Firebase and so on. Basically it is just a fat interface with a long list of event logging functions, like logSignIn(), logSignOut(), logSellProduct(), logOpenMap() and so on. There are about 40 such methods in that interface. So this is how we implemented it in the first place.

Expense Report Case Study

2 minute read

One day, I was watching another Uncle Bob’s video (yes, they are addictive), when I see one example he gave when talking about open closed principle, it ringed a bell in my head. This looked familiar! The type in some data classes, some switchs or ifs, some &&s and ||s all dancing around in the class. I can almost hear them teasing: “Come and catch me! Come and catch me!”.