Code without tests is bad code. It doesn’t matter how well written it is; it doesn’t matter how pretty or object-oriented or well-encapsulated it is. With tests, we can change the behavior of our code quickly and verifiably. Without them, we really don’t know if our code is getting better or worse. — Michael C. Feathers
This is an attempt to help developers write better test codes.
Writing tests first is not difficult at all. Once a programmer adheres this pattern, it becomes a habit which helps to view systems inside-out as well as outside-in, and end-to-end. But to do…
Even after years, this post yet remains the best to describe what actually load-balancing is. One of my goto resource when ever I am thinking of a distributed system design. Again, thanks Matt.