Lessons learned in May 2016
This is what I learned in May 2016: Read about State of Code Quality in 2016. Apparently, CodeReviews are the most important tool to ensure code quality....
This is what I learned in May 2016: Read about State of Code Quality in 2016. Apparently, CodeReviews are the most important tool to ensure code quality....
Today I wanted to introduce Degraph in my project to track cyclic dependencies. This got me a java.lang.IncompatibleClassChangeError which I had never seen b...
This is what I learned in April 2016: GitKraken is awesome. I generated an SSH-key with GitKraken and noticed that it gets uploaded to your GitHub accoun...
Some of the problems in everyday software development are luxury problems. Like when you work in a greenfield project and are able to choose how you implemen...
Microservices are one of the hype topics I didn’t manage to have a look at. So this week I was lucky finding that the cover story of the Java Magazin (issue ...
This is what I learned in March 2016: Installed and began using GitKraken. Pretty nice Git client! Enrolled in the Udemy course “Spring Core - Learning...
This is what I learned in February 2016: There have been some interesting situations in a project I used to work in. These gave me the idea to write an a...
Automated tests like JUnit are a mandatory part of developing software. Recently I saw some bad things happening in a project that are good arguments for aut...
Yesterday I noticed there is an important topic missing in my JavaFX workshop: Internationalization. So here is a SSCCE for that. It’s basically a copy of my...