Skip to Content
After a visit on the first day of the Computer History Museum in Palo Alto, where SAP’s guru-hackers and elite-coders could look at artifacts of the computer age, like the lizard (predecessor of the mouse), the first cursor (just recently found during the removal of a horse-stable in Palo Alto) or the utopic concept of a bug-free program (the concept paper is locked away deep inside a mountain in the Antarctic by the initiative of the software industry, especially due to heavy lobbying work of their support departments), the hacker-elite and coder-geeks decided on names for their teams and their team mottos. Here is, for the first time in history, the full and uncensored list:

Team 1: Tiger – Passion to make a difference
Team 2: ABAP-Avantgarde – To boldly code where no man has cored before
Team 3: Extreme Experts – What is R/3?
Team 4: Frontrunners – Collaborate, Invent, Demonstrate
Team 5: The Mind Mappers – Leave no white-space
Team 6: NW Emergency Task Force – The motto-less
Team 7: 007 – The World is not enough
Team 8: WebXperts – Contribute to the next Big Leap

Energized and freed of their jetlag, the second day started for our code-hackers and elite-gurus. On the agenda was a full day of “Agile Programming” training, with hands-on examples. While the Frontrunners sat in the first rows, having the dead-animal breath of the Tigers in their neck, the ABAP-Avantgarde sat in the last row. The James Bondeses tried to Mind the Mappers, and the NW Emergency Task Force spent the whole morning fixing the problem of the coffee machine (no milk). When they finally found the bug, the coffee machine was already reconfigured and pours now coke. Actually, coke and steamed milk is really worth a try. Only the shy Nameless hid behind their screen. And the WebXperts followed through a web of video-cables, giving their team name full honors.

Agile Programming for the code-gurus

But all of them, and there was no exception, really all of them sat nail-biting and trembling in front of their keyboards. When can they hack, when are they going to be unleashed and smash their code into the machines?

We have to mention that the organizers had to consider an atypical risk, that 40+ guru-geeks pose in an earthquake zone like in the Bay Area with San Francisco. We all know that computers get heavier every day, when you program. Every line of code entered is stored on the hard-drive and increases the weight. While this is OK for regular programmers, this can pose a significant threat, when having 40 of the most exceptional eight-armed code-typers assembled at a fragile place like this. Gazillion of lines of code in just one weekend by 320 arms, and we’ll have a magnitude 9 earthquake with lava swallowing every computer that’s available.

Earthquake prevention: the design phase

The organizing committee under the leadership of Guido S. therefore decided to have the geek-gurus first focus on the design of their work, before they start their hacking-orgy. Indeed, you will see the next days, if the web log updates will appear in time on SDN, of if we all went to hacking-hell.

Before I finish, we have some messages to be posted. One is from Stefan B. “I miss you, mum”, and the other one from Yong L. “Hi honey, did I turn off the gas in the kitchen?”

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply