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

Welcome! 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

Dec 2017: The new ThoughtWorks Technology Radar is out and I'll present it with my colleages, Birgitta, Christoph, and Lisa in Hamburg, Munich, and Berlin. more

27 Nov 2017: At HEALTH:CODE my collegue Lukasz and I will present a version of my DevOps talk with a focus on the Medical Industry. more

Latest blog posts

The Swift effect

17 Jan 2018

In June 2014, at its annual developer conference, Apple announced that they had created a new programming language, named Swift, to replace the ageing Objective-C as the preferred language for writing applications for Apple devices.

I remember this well because also in 2014 I had decided to revamp the API for OCMock, a testing framework for Objective-C that I have been maintaining for a long time. Most of the work on the framework was done in April/May, and the Swift announcement came just days before the release of the new version of OCMock.

Immediately, I wondered what impact of Apple’s announcement would have on Objective-C and, in turn, on OCMock. Given Apple’s messaging around this, it was clear that most developers would eventually move to Swift. But how many? And how quickly?

Read the rest of this entry

Using multiple Github accounts

21 Dec 2017

Two Octocats

Mixing work and private life always brings its problems. That is also true for open source software, and for being a member of the communities on Github. In my case, I have a number of repositories on Github that I would classify as personal; they are not linked to my work at ThoughtWorks. Some of these are significant projects in their own right.

At the same time, an increasing number of clients I work with at ThoughtWorks keep their source code on Github. And to be specific: they use itself, not the on-premise Github Enterprise version. It never felt right to use my regular Github account in such cases, and I experienced real issues because of it. For example, one client regularly ran Gitrob, my membership in their repositories was a link to my non-work repositories, which Gitrob also scanned. Due to the way it works Gitrob has a tendency to report false positives, needlessly causing concern and extra work for the client team.

So, to avoid such issues I created another Github account purely for work. Easy as that? Turns out there is a significant problem; a problem that now has simple solution, but one that is difficult to find.

Read the rest of this entry

more blog posts

Popular content

Open Source projects:



Active Github repositories


all repositories