"Quiet time" at work

Posted by Patrice Neff Sat, 20 Oct 2007

Intel is doing a quiet time pilot with about 300 people. In that pilot they disconnect for Tuesday morning. No mails, no IM, no phones, no person allowed to walk in to the office. The pilot has launched end of August, but I only learned of it today through another story on the same blog: No Email Day (via NZZ). On Friday they now encourage not using email but instead talk directly face-to-face or use the phone.

I like the idea of quiet times a lot. In fact at local.ch we’re implementing something similar since a few weeks. Every morning from 10:00 to 12:30 no interrupts are allowed – at all. There is the exception of Thursday which is our meeting day because most of our partners are around on that day. But for the other days it means that you can’t walk in to co-workers during that time, our Skype clients are switched to “Do not disturb” and many people shut off their mail clients. Skype is by the way quiet intelligent about it’s “Do not disturb” mode – any message that comes in gets queued. While you can access them if you need to, they are not pushed into your face.

The times are not arbitrary. Most of us come to the office at 9 in the morning. Beginning the quiet time makes sure that everybody can start gathering the required notes and feedbacks needed for the morning work. Then when people switch into quiet mode at 10, they hopefully have all they need to get their work done. The end is defined by our lunch break which usually starts at about 12:30.

The other idea Intel is implementing doesn’t sound very interesting to me, though. While the concept of “no email” sounds good their motivation stucks me as strange. Walking in on people or using the phone steals a lot more of the attention then sending a mail. You can turn off your mail client or switch off the alerts. And actually I’m doing that. I check my mail only about every second day. The rest of the time my mail client is turned off.

Mail testing with Selenium

Posted by Patrice Neff Thu, 23 Nov 2006

For the next phase of local.ch E-Mail processes will play a central role. So I wanted to include those processes in our Selenium tests. It’s actually quite easy to do.

First create an account where test mails can go to. That account should be accessible by one of your scripts. I use a normal IMAP account for that. Then write a script which always outputs the newest mail on that account. I include some of the important headers plus the body (body parts for multi-part mails). I also made that page refresh itself every two seconds.

Then writing the tests is easy. Write a test first that executes the action that sends a mail. Make sure the mail is sent to your test account.

Next write a test that opens the getmail script (using the selenese command “open”). Follow that with a waitForTextPresent action to wait until the test mail has arrived – which never lasts more than a few seconds in my environment. Then you can use the normal test commands such as verifyText, verifyTextPresent or even click etc. if you output HTML mails correctly.

Works like a charm around here. If there is interest I can publish my script to get the mails. It’s written in PHP and is basically an IMAP client using the two PEAR packages Net_IMAP and Mail_mimeDecode.