I think it was around 2009 when I started reading a book called Clean Code by Robert C Martin (a.k.a Uncle Bob). I found the book on a so-called ‘top 10 must-reads’ for software engineers. I really enjoyed reading that book. It had a pleasant writing style, well structured and provided some valuable insights. A few years later “The Clean Coder” was published and what appealed to me this time was that it was a book about some of the other aspects of our trade: professionalism, handling pressure, clear communication, etc. If you have not read it yet or are looking to improve some of your softer skills I would recommend reading it.
Three weeks ago I presented at Luminis Devcon 2018 about the challanges of designing and documenting REST APIs. The reason I gave this presentation was that about 8 months ago I started on a new project for which my team had to develop a public facing REST API. Having a good documentation for such an API is very important, since users will read the docs and have an opinion about the usage and correctness of such an API. During my presentation I went into the lifecycle of an API and how to maintain the documentation in such a way that it’s always in sync with the actual API, since these can easily drift apart.
I’ve been trying to make this a tradition, but last year I had too much going on in my personal life, which resulted in skipping my ‘year in review’ post. 2016 was really hectic, but everything seems to be back on track now. To shed some light on what happened professionally let’s take a very quick run through 2016.
Recently I’ve been spending some time with Cucumber and joined the cucumber gitter channel when somebody pointed out that they were having trouble running Cucumber from the command line. I usually run Cucumber from Maven, so I thought it would be interesting to see what was required to run cucumber from the command-line.
At my current project, we’re developing an application based on Spring Boot. During my normal development cycle, I always start the application from within IntelliJ by means of a run configuration that deploys the application to a local Tomcat container. Spring boot applications can run perfectly fine with an embedded container, but since we deploy the application within a Tomcat container in our acceptance and production environments, I always stick to the same deployment manner on my local machine.