Saturday, February 13, 2010

Piraat

How many times have you found yourself quoting: “What ? that looks like half a pint of beer and half head”

Well I can assure you if you are ordering Piraat off the tap you are most likely to find yourself with the _MG_4103-1same statement. And half way through your pint you could be a happiest person around the table.

Belgians have learnt the art of brew over the ages and some of the finest beers in the world are from Belgium. Piraat is my favorite Belgian brew along with St Bernardus Abt12.

Piraat has a very high alcohol percentage (10.5% by vol) and before you finish your second pint the tasting glands go numb. But that first pint is enough to make you realize how good it tastes. It has a sweet citurs aroma and a fruity taste leaving behind a tinge of hoppy bitterness. It tastes better when poured from the tap in an exclusive piraat glass, in that golden color. Beer quantity is 3 quarters of the pint and rest is the head.

If you are one of those who believe in getting hammered to have most fun on a sat night without spending a fortune on drinks in a hefty club… 2 Piraats’ before the party can make it a memorable one.

Wednesday, February 03, 2010

Livesite Support – Who should do this?

Customer service is the first line of support for any e-commerce. Traditionally these people have admin rights to the system and written instructions to follow them.

Second line of support when something goes down on live site is to call the developer on pager duty. Workaround for the problem is found and fixed on a ASAP basis and then we tend to stick with the work around forever.

Kayak has this great idea:

Why would you pay an engineer $150,000 to answer phones when you could pay someone in Arizona $8 an hour?" If you make the engineers answer e-mails and phone calls from the customers, the second or third time they get the same question, they'll actually stop what they're doing and fix the code. Then we don't have those questions anymore.

Pager duties are not fun but why Developers should be the only one to be quad-damaged by them. It should be a shared duty of the team. The tester on the team should be equally responsible for it and at the same time the program manager too.

These 2 other disciplines have their own excuses to escape such responsibilities.

QA/PM: I didn’t write the code, I don’t know the fix, how am I supposed to handle it.

You as a part of the project is expected to have a level of debugging skills, or investigation and identifying the cause based on symptoms. May be the code is right and its a network issue or service is down. Could be a false alarm etc, may be something needs to be bounced. If things are beyond your understanding I am sure developers will be more then happy to help you out. Also the ground work on investigation is going to help in getting things fixed earlier.

Its hard to sell this idea to these disciplines but then there are some smart asses who know how to frame and sell it and here’s an example:

This is a great opportunity to be close to our real customers and it will be a good learning experience for everyone to be involved in this highly visible customer service exercise. Remember that as a pager carrier, your only responsibility is to triage the issue and escalate them if necessary. Developers will always be around to help out if there are any questions.