Make sure you didn't miss anything with this list of the Best of the Week in the DevOps Zone (March 13 - March 20). Here they are, in order of popularity:
Don’t let the good enough be the enemy of the perfect. Your first set of test will be garbage. As you stick with it, you’ll wonder what you were thinking when you wrote your first test. But this should not deter you. This is what happened when you first started coding. Maybe it is still happening. No worries. It is the practice that will make you better able to write tests and better able to write code that is testable.
I was looking at a bit of code was leaking class loaders when deployed to tomcat - so I wanted to quick rule out that a background Thread was holding onto the loader.
As you start your journey down the road of Unit Testing you will discover that part of what makes code testable is this concept of Dependency Injection. As you explore further, you will see people mentioning various Dependency Injection frameworks.
Any design is a choice. All problems have multiple solutions, and the current design you have was the chosen one. It may also look like a giant god class (or a demon class, like our subject in the picture). It’s like that because you (and others) have made design choices over weeks, months or years not to tidy it up.
As developers, we all love shiny new things. New technologies, new languages, new hyped conversation starters. And everyone seems to have an opinion about why you should do this architecture, or why you should use that language. At the end of the day, your employer is expecting you to deliver using a means to an end, but what is that end?