Andreas Zeller

Andreas Zeller (high resolution photo)

Andreas Zeller is faculty at the CISPA Helmholtz Center for Information Security and professor for Software Engineering at Saarland University. His research on automated debugging, mining software archives, specification mining, and security testing has proven highly influential. Zeller is one of the few researchers to have received two ERC Advanced Grants, most recently for his S3 project. Zeller is an ACM Fellow and holds an ACM SIGSOFT Outstanding Research Award.

Phone:  +49 681 87083-1001
Twitter:  @AndreasZeller
GitHub:  andreas-zeller

Hosted on GitHub Pages — Theme by orderedlist

2 July 2014

if you plan to invite me for your upcoming event, please avoid nightmares like this one

by Andreas Zeller

I frequently get invitations to give talks at conferences, summer schools, and other events.  Normally, it is an easy thing: I check my availability, agree, book travel and hotel, prepare and give a talk, have fun, get reimbursed.  Not so with this recent summer school in France, though.

January.  I get an invitation to lecture at a summer school in France.  Sounds fun and exciting, but it is in our exam week.  I go for a compromise: I accept, but will be able to join only for one day.  As usual, I don't get paid for such events, but the trip will be taken care of.

February.  The organizers ask all speakers for a flight connection, such that they can book a flight for us.  I spend an hour looking up possible flight connections on Expedia, only to find that the plane will be cumbersome and expensive.  I send the quote, adding that going by train will be cheaper and faster, an assessment shared by the organizer.

February.  The summer school asks me for a quote of the train ticket.  This is not possible yet, as the ticket can only be booked three months in advance.  I give an approximate price based on next month's connections.

March.  I send title and abstract and state my availability for the lecture (Tuesday or Thursday).  Everything is fine.

April 17.  The summer school produces a flight itinerary and asks me to confirm the booking.  Flight?  I reply stating that we already agreed to have me travel by train; I again retrieve and provide a quote for the train ticket.  As the flight itinerary assumes that the talk be on Wednesday (which does not fit me), I ask that my talk be moved according to my availability.  The organizers agree.

April 17.  In return, the summer school produces a train itinerary, again asking for confirmation.  The itinerary also assumes my talk is on Wednesday.  I cannot confirm the itinerary, repeating that the date does not suit me and that my talk date will be moved to either Tuesday or Thursday.

April 22.  I get a tentative program, where my talk is scheduled on Wednesday morning.  This is the day on which I am not available, and I curse between my teeth.  I again ask for the talk to be rescheduled.  The organizers apologize for their mistake and schedule my talk for Thursday.

April 29.  I get an electronic train ticket.  This booking is still the same itinerary as on April 17, assuming my talk would be on Wednesday.  I am pretty upset and state that the ticket neither fits my schedule nor the revised schedule of the summer school.  Rather than exchanging more mails, I suggest I book the ticket myself, saving time and money.

April 30.  The organizers apologize for their confusion, and ask me to please book a ticket myself.

April 30.  I book a train ticket on the SNCF site.  This takes me 10 minutes.  I send the itinerary to the organizer, who again apologizes.  All seems to be set.

May.  The administration asks all speakers for bank account information, address, and passport copy, which I all provide.

June 5.  I get a hotel voucher for my stay.

June 27.  The organizers ask all speakers for rechecking the information on their Web site.  I am busy in a PC meeting and postpone the check for a few days.

July 1.  The organizers urgently ask me if it would be okay for me to chair a session on Wednesday morning.  Wednesday?  I will be traveling on Wednesday morning, so no.  I remember the earlier message to recheck all information.  It turns out that on the Web site, my talk is still scheduled on Wednesday, and my hotel is booked wrongly, too.  As I realize this, I jump up and scream, literally banging my head against the wall; my secretary comes in and asks whether everything is okay.

July 1.  As I cool down,  I write to the organizers. I repeat my travel details and for the last time, ask the organizers to reschedule my talk as confirmed multiple times.  The organizers again deeply apologize for the confusion and promise that the schedule will be fixed.

July 2. [Update]  I cancel my participation, wishing all the best to the summer school, and bearing the ticket expenses myself.  I feel relieved and relaxed.  All is well that ends well.

Lesson learned #1: While this trip has easily caused me more trouble than all my other trips combined, let me state that almost all of my business trips are painless, including all my trips to France so far.  Also, other lecturers at the same event report that their booking all went well, so I guess I just had a long series of unfortunate events which is not typical for France at all.

Lesson learned #2: If you organize an event, make sure you have a single point of contact – there should be precisely one person to talk to the invitees, who keeps track of all information and (possibly) interacts with the administration.  Do not have your administration interact with the invitees directly, bypassing you; likewise, keep the administration updated at all times. tags: