Dependency Injection with annotations is now a widely spread practice in the Java world. If you use them, are you able to keep a tight encapsulation and still inject mocks or alternate implementations for testing?
Way too often I see people being obsessed with a system which provides automated failover when they have a system of way too small case, have little discipline, and implement solutions not following best practices and do not test it properly.
So far we know how to implement graph depth-first and breadth-first searches. These two approaches are crucial in order to understand graph traversal algorithms. However, they are just explaining how we can walk through in breadth or depth and sometimes this isn’t enough for an efficient solution of graph traversal.
What could be more boring than capturing credit card data on a form? Well, it's actually not that boring -- since you may want to encrypt this particular data, which presents its own set of challenges.
This article will discuss the use of non-first-normal-form designs, in particular the storage of arrays of tuples in columns to simulate a nested table. The possible uses and problems of such a design will be discussed in detail.
If you are throwing release parties, or just relieved every time the release doesn’t go wrong, it’s probably time to look into DevOps techniques and automating your releases. It’s not like the business is going to want to slow down the pace.