A good question, why you need Katas to be a better programmer. I won’t answer this question fully but I try to explain why Katas are good and why you should do them if you can.
As mentioned in the previous article I’m going to write some words about dependency injection — with Spring. As stated before there exist a lot of good books and articles about DI and I will only tell my opinion of the usage of DI. And I’ll focus on DI with Spring. Eventually I’ll take a look at JSR-330.
As a little milestone in the “Variations” project I’ll introduce Spring as a configuration and dependency injection framework, inversion of control container and so on — after the big part Liquibase.
I will not give a full stack introduction to Spring. I suggest you to read a book in this topic, there are many good introductory and pro books about Spring on the market. If you want to have an application quickly up and running search between the guides on Spring (take a closer look at Spring Boot).
The integration with Spring is not a big thing. You only have to configure your data source, the Liquibase bean and that’s it. OK, this sounds simple but there are really some pitfalls if you’ve never done this.
For integrated testing I set up a Travis CI account to have a continuous integration tool for my Variations project — because sometimes a local build yields other results than a build on committed sources. Mostly if you forget to commit something or you use a dependency which is not properly configured in maven or gradle.
And now I’ll tell you how I did that.