• Don't convince your coworkers to do TDD.

    At the beginning of the year I had a little twitter discussion about TDD. It started of as a request for some documentation about TDD. But after some back and forth it turned out that the goal was to convince the members of a team to adopt TDD in order to fight quality problems.

  • Working on the Spring Data Team.

    It’s now over 9 months since I joined the Spring Data Team. Time for some looking back.

  • Project Reactors flatMap - a Closer Look

    An important part of reactive programming is backpressure. The idea being that only those events get published, that can be processed by the downstream operators. That’s why the following code prints ten lines as one might expect:

  • Are 200 Push-Ups too much to be healthy?

    Wow, it’s over three years since I published the article about me picking up running. That means I’m now running for 4 years and it’s time for an update.

  • Branching strategy of the Spring Data projects.

    Before starting to work on Spring Data I hardly ever used git rebase. Everybody in those teams was happy when a commit comment included some useful comment and the id of the issue. Some even considered to much. And no one really worried about a discussion of the benefits of merge vs rebase. Therefore working on the Spring Data repositories was some serious change for me since heavy rebasing is an integral part of the workflow. But after some getting used to it I really like the approach and I think many teams might benefit from something similar. So a blog post is in order:

  • Brace for impact.

    I really prefer keeping myself busy with technical stuff rather than with politics. But sometimes things happen that are so stupid that they affect me and I have to speak up. And sometimes those two areas intersect and politicians with their incredible belief that they can ignore reality and technology make me want to puke.

  • No Spring One for me.

    Shortly after signing my job contract with Pivotal, my awesome boss told me to reserve time in December 2017 for the Spring One, because it is the event where almost all the Spring developers meet once a year.

  • Multithreading with Reactor

    I recently started working with (ok, fooling around is a better wording) Reactor, a reactive library that gets used by the new reactive parts of Spring. I’m especially interested in how multithreading works with Reactor. So here is what I learned so far.

  • What's Your Next Language?

    A common recommendation for software developers is to learn a new language each and every year. While I consider this a little over the top, learning a new language from time to time is certainly a good idea, but what language should you pick?

  • Work Breakdown Structure vs Backlog

    Lately people keep telling me that things that are common practice in agile projects are done in waterfall based processes as well. And you know what? Some are. But others aren’t and again others are completely missing. So lets make a loose series of articles about waterfall artifacts and practices compared to matching agile artifacts and practices.


Wan't to meet me in person to tell me how stupid I am? You can find me at the following events: