This website does not display correctly in Internet Explorer 8 and older browsers. The commenting system does not work either in these browsers. Sorry.

erik dörnenburg


I'm Erik Dörnenburg, a software developer and consultant. I work at ThoughtWorks, where I help our clients write and deliver custom software. Somehow I also find time to speak at conferences and to maintain a couple of open source projects.  more

News and Events

6 June: The commenting system for this site was moved from Heroku to Uberspace and it's working again.

30 June: Together with Philip from AutoScout24 and Markus from Amazon, I talked at the AWS Summit in Berlin. more

11 Sep: I'll present my thoughts on Architecture without Architects at GeeCON Microservices.

Latest blog posts

Privacy and this website

03 Aug 2015

api_controller source code

Privacy on the internet has always been important to me. I guess this is because I grew up in Germany where, in no small part due to experiences with the Nazi government and, later, the Stasi in Eastern Germany, people are generally more privacy conscious. For example, when the implications of the 180-day rule in the US Electronic Communications Privacy Act really sunk in, I moved all my personal email hosting out of the United States. Last year, I finally realised that I should talk about privacy and mass surveillance more publicly, which I then did; in a talk, in a group interview on privacy and security, and an interview about the Pixelated project.

At the same time I'm running this website. Do I put my money where my mouth is? What am I doing with this website regarding your privacy?

Read the rest of this entry

Java at WWDC

17 Jul 2015

Picture of WWDC KeynoteThis year, the Java programming language is 20 years old. To mark the occasion, Michael Stal, editor of JavaSPEKTRUM, decided to publish a few anecdotes that we, the members of the content advisory board, would contribute. When I thought about what to write the hype around this year's WWDC was building up, reminding me of the following story.

It is May 2000. A few colleagues of mine and I sit in an overcrowded room at Apple's World Wide Developer Conference (WWDC), looking forward to session 407, to be presented by Rory Lydon. We're here because at our company we work with Apple's WebObjects application server, one of the very first application servers. Originally written by NeXT in Objective-C to be used with Objective-C it moved to Apple as part of the NeXT acquisition in late 1996 and was made Java compatible.

Rory is going to tell us what is going on in one part of Java land and his session has the title “WebObjects: EJB – Making the Best of a Bad Thing”. After an introduction he continues with a description of core parts of the EJB specification, and many in the audience find hard to believe what they are hearing. Rory quotes from the specification, compares with the elegant solutions in WebObjects that have matured over years. The listeners frown, worrying how their applications could be implemented with this EJB technology. The specification itself is the target and Rory mercilessly points out gaps and weaknesses. After further quoted passages from the specification the mood in the room brightens and, arriving at bean and container managed persistence, the first laughs can be heard. “This will never work in this form”, many seem to think.

Read the rest of this entry

Three mysterious hardware problems

29 Jun 2015

PSULast month three completely unrelated, yet equally mysterious, hardware problems kept me entertained at home. Each did have an obvious explanation in the end. Getting from symptoms to diagnosis, though, required both, guesswork and luck. Sure, I'm more of a software guy but I thought that I had a decent understanding of “how stuff works”. Well, looks like things have gotten pretty complex now.

Problem #1: our trusty PS3. Symptoms: We had just bought a new TV. Excited to see how games would look like on it, I powered up the PlayStation, and was greeting with a big blank screen of nothing. The TV was definitely set to display the correct input source, but, still, there was no picture. Swapping the HDMI cable to a different port on the TV, with the PS3 running, fixed the problem. It definitely left an uneasy feeling, though.

Things got even more confusing when I tried to play again another day and was again greeted with a blank screen. Now swapping back to the HDMI port that I had originally used gave me a picture. How could that be?

Read the rest of this entry

more blog posts

Active Github repositories

all repositories