Lessons Learned in July 2016
This is what I learned in July 2016: Pitest.org is a mutation testing toolkit. It changes the code under test (not the test themselves!) by applying seve...
This is what I learned in July 2016: Pitest.org is a mutation testing toolkit. It changes the code under test (not the test themselves!) by applying seve...
Since a couple of months, I have an idea that I cannot implement because of other priorities. It’s about a project regarding mentoring in the IT. I understan...
Since the beginning of this year I’m working in a remote team. There are two developers in Romania and me in Germany. To successfully develop software in thi...
This is what I learned in June 2016: Although this may sound like from a bad movie, my computer acted pretty strange recently. While desktop sharing with...
Because I recently read about this pattern, here are some words about how I use DTOs, Data Transition Objects. DTOs are used to transport data, for example f...
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...