First Steps With Degraph

A crucial part of implementing software components is to get your code free from unwanted package dependencies. But most of the time it is hard to get an overview of which code depends on each other. SonarQube is a great tool but unfortunately they dropped the Package Tangle Index analysis support (see 'Also worth noting' here). JDepend is another tool but I could not really get familiar with it (even not with the eclipse IDE integration). Thus I decided to try Degraph - a newer tool that I heard of some time ago.

Logging request/response messages with Apache CXF

Today I would llike to give a short introduction in How-To log request/response messages of your Apache CXF JAX-WS service.

Software deserves documentation

Building software is a tough process. A lot of disciplines are involved to specify the requirements, to define the software architecture, to manage the data, to test, to integrate and to run the software and possibly to do a lot more thinks. Different processes - from waterfall to agile - try to handle these tasks in different ways and they produce different documentation artifacts.

My Technology Radar

ThoughtWorks published a recent version of their Technology Radar these days and Neil Ford did some explanation on it with the recommendation to "Build Your Own Technology Radar".

I thought this is quite a good idea and so I wrote it down. Keep in mind that I am a Java backend developer so the topics that appear in this radar are affected by this.