Too Long; Didn't Read
A blog featuring in-depth posts about Python, Scala, TDD, devops, security and all things devops. The "Design Patterns" original book states that your design should be specific to the problem at hand but also general enough to address future problems and requirements. The most important thing to understand is the requirements, both the present and future ones. Only with clear requirements in mind, one can effectively design a solution, possibly tapping into the great number of patterns that other designers already devised.
Share Your Thoughts