On the first day of Christmas….

My secret Santa gave to me, a smashed-in driver’s side mirror.  I may have mentioned that in a post on Monday.  I’m still troubled by it today, having left work early yesterday to take the car in to get an estimate from the insurance company.  The estimate was around $250 — well under my deductible.  Of course being that my car is so new, the pricing wasn’t even in the Allstate guy’s computer yet.  That didn’t make me feel any better.  So let’s add a half day’s work onto the $250.  So far some jerk who couldn’t be bothered to do the right thing is costing me my plasma TV.  After I wind up with a ticket because I have improper mirrors (since I couldn’t get in to the shop until next Friday) we can tack on a few dollars.  I can’t forget the time out of my day lost on the car being in the shop, I’ll be well over my deductible, but of course, the insurance company doesn’t count my time running around and the secondary effects.

At DDA we hope that our clients don’t feel like I do right now, inconvenienced and annoyed at a process that takes more work on top of an already pricey process.  Our clients do not want to know how hard it is for us to do something, they just expect that it is done as painlessly as possible for them.  In fact, we have many clients who would rather us do as much of the work as is possible, with little or no feedback — just to get it done.  Usually when we quote a programming project, we don’t have something quite as solid as a car part to be fixed.  It is usually a mess of ideas on how things need to end up, with no real process to get there.  They may say they want a car, and we’re thinking Kia, but in the end they wanted a Mercedes.  In the end, as a programmer, we have to balance what it is we quoted with what it is that they want, saving as much aggravation for all parties.