Freedoms of working at CQSE
I often get asked by friends why I stick working at CQSE for almost six years now. One reason simply is that I’m quite free in arranging my workday in a way that it fits for me. Hence, I’ve recapitulated a (not so typical) workday on my company’s blog that illustrates the benefits and freedoms of working at CQSE.
Our Journey to GIT—One year later
The migration of our code hosting from Subversion to Git enabled us to scale and professionalize our development process. This post on my company’s blog sheds some light on changes the migration allowed (or forced) us to perform.
Our Journey to GIT
This post on my company’s blog summarizes the the hurdles I had to take when migrating our code hosting from Subversion to Git: I had to combine the history of several Subversion repositories into one large Git repository and cleaning history from unneeded and big files. Oh—I also had to find an alternate solution for these cursed svn:exterenal links.
Lessons from Code Reviews in the Wild (part 2): Get rid of unnecessary code
This is the second post of two posts concerning code reviews on my company’s blog. This time I emphasis on one of the benefits of code reviews: Getting rid of unnecessary code.
Lessons from Code Reviews in the Wild (part 1): There is no exhaustive Review Checklist
This is the first post of two posts concerning code reviews on my company’s blog. I’m motivating why code reviews are an essential part of our daily work (also besides code) and then giving some insights why there is no exhaustive review checklist—a question I often got asked at customers when introducing peer reviews.