I think you're a good person, but I can't be with you. I have to break up. Sure 2007 was a fun year, galloping around the estate with that thick scent of delicious coffee in our hair and eager for the new dawn of a dark roast. We had some good times. The Techni Vorm label made me feel European too and I tried to embrace it, I really did. Its not you, its me.

It wasn't easy with your friend, Virtuoso, the coffee grinder. He never made it simple for us. I don't think he ever really accepted me. What was up with that static electricity? It let forth a brilliant shower of charged coffee grounds after each use. I'm mean really, how can he expect to keep someone around? Sure his sleek exterior and large bean reservoir would make anyone grin, but I've got to think of myself sometimes, I have to ask, what's in this for me? It was just too much of a mess to clean up after every grinding session.

Mocha Master, why did you start spilling over? At first, I was willing to blame it on the other people you saw. There were several accounts sent around on how to properly make coffee. But time and time again, you spilled when no one was looking. The final straw was when you spilled yesterday for me. It was me Mocha Master! I was here all alone with you and yet you forsake me. How could you do it? You know the level of coffee grounds in there was well within the accepted norms. Somehow you clogged up and spilled over the counter just like all of the times before. I have to give you up.

Hello Mr. Coffee, its been a while. I know I've been a bad friend and traipsing all over the coffee producing regions of the globe with my European friend, but its over, I swear.

I see you've gotten some new buttons and they look great, all shiny and in different colors. I've even started using a carafe so you don't need to worry about burning the coffee and ruining the flavor.

Oh, and hello little grinder! How have you been? I sure do miss you. Sure, you're from Starbucks, but that's ok. You're a good little guy and you don't have any static electricity. We love large machines and small machines alike. Sometimes you're abused and blamed for a mess, but its far and few between and I know you mean well. You can't fight gravity! Plus, you can grind your beans in 10 seconds flat. I'm going to enjoy seeing you around.

Mr. Coffee, I want you to know that I'm ready to get down to work and you won't have to worry about any more whimsical adventures from me. We have a simple agreement in place; you make coffee and I'll drink it. We don't need any drama in our lives around this matter and neither of us wants a high maintenance relationship. I'm glad you were willing to come back. I love you Mr. Coffee.

I was fortunate enough to pop up to a special event on Silverlight at Microsoft in Redmond, WA today. Mithun Dhar, Laurence Moroney, Arturo Toledo, Adam Kinney, Ernie Booth and Jesse Liberty gave us some sweet tips on building apps and organizing a good workflow between developers and designers.

Arturo is an awesome graphical designer. Oddly, or perhaps not, I liked his presentation the best. He made the Expression products fly and gave me (a developer) good tips on working efficiently with my design team. Jesse was a close second with his fundamentals presentation - he really clicks well with developers.

The crowd was mixed with about 60% developers and 40% graphic artists. I saw the ScottGu blog post this morning announcing that Silverlight 1.1 is now named Silverlight 2.0 - between that and the hints dropped at today's meeting, it feels like Silverlight is getting ready to explode. I think I'll still remember this day very well in three to five years.

http://www.justsayhi.com/bb/html_quiz

I forgot some easy ones like <div> and I thought I typed <fieldset> because I also got <legend>, but a respectable score; maybe? ScottV got a couple more than me.

I got a favorable message, so I reckon its not all that bad.

http://www.lhotka.net/weblog/MagenicWantsYouThisTimeWithAQuiz.aspx

After all, Rocky got an 84. I think I rocked most of the ASP.Net questions, but the smart client stuff and multi-threading is a little foreign to me.

What did you get?

Under ordinary circumstances, all three of my blog readers know that I don't like playing blue. Yet sometimes, it is the only possible response.

This is to the 1998 Honda Civic Headlight Replacement Technical Writer:

You Suck.

I'm no mechanic, but I have replaced my car battery, and I'm generally aware of what goes on under the hood. Plus, I'm a good reader. I can follow directions. In my older cars, the bulb was encased in the complete housing. A few screws and a plug-and-play later was all it took. Not so today. All you get at the store is the actual bulb. Much smaller and easier to ship.

The following images show the 1.5 page description of how to replace a light bulb in a 1998 Honda Civic.

The instructions for headlight replacement begin on the right side of the following page. The author notes some good points to understand before tackling the job.

Then, it gets into the meat of the job with a full page shown in the following image.

As you can plainly see, at no point does the author state the following truth:

If you are reading this manual, then your best course of action is to return it to the glove box and drive to your nearest Oil Can Henry's location. Request a bulb replacement and happily pay the fee knowing that (a) you didn't have to do it (2) you didn't break anything; aka, less swearing and (iii) the delta between the cost of the bulb at the NAPA auto part store and what you paid at the shop are negligible.

And for that malfeasance, this technical writer sucks. It is my opinion that anyone replacing the driver's side headlight in a competent manner would not need to resort to the manual. For if they did, it would be a clear indication of the pain to come.

For starters, a light source for working under the hood is a good idea. I used one of these pod lights. Press the light to turn it on and off. They're small and nimble.

So here's what we're dealing with. The drivers side headlight sits squarely in front of the power steering reservoir. The following image shows my finger on the reservoir. Its connected by one hose on each side and is seated on a small cradle. You can already begin to see the terribly small spaces we're about to engage.

Just from the previous photo alone, you can see how the designers failed with this bulb location on the 1998 Honda Civic. Per the instructions, I am to lift the power steering reservoir out of the cradle and push it aside so I can gain access to the bulb housing. Those two hoses that attach to the reservoir aren't too keen on movement. I finally ended up disconnecting one of the hoses and stuffing it with a rag to stop the flow of power steering fluid to my garage floor. There was quite a bit of cussing to just reach this state.

Now that I had the reservoir propped up and out of the way and the power steering spill slowed to a slow dribble, I could being the real work. The following photo shows an overhead view of the bulb housing and my light source nestled into a good crevice.

Next, I need to pinch the tabs of the bulb housing to release it. This is very important, so you would think that the book would do a good job of describing where they are and what they look like. Not so. The tabs are nearly invisible, even with great lighting. They're about the size of a small pea on each side as indicated in the following photo. Before learning this, I cracked the plastic housing on the bulb housing with the pliers. Go me!

After the bulb housing is removed, the rubber seal and wire latch can be removed to produce the following item of grief - a blown out halogen bulb. I bought a new one at NAPA for $8.00

When you're wrestling with the wire that provides a constant pressure on the bulb housing and keeps it in place, be careful not to snap off the little plastic tab that hooks onto the wire; that's bad. Grrrrrr.....

Finally, I drove (the other car) to the NAPA auto parts store (again) and purchased a small amount of power steering fluid. When I arrived, the very nice man behind the counter saw the section I was looking and advised me on a good brand of leak sealant. I explained that I actually wanted power steering fluid. Sizing me up accurately, the man tilted his head and asked why I wanted power steering fluid. Evidently, I didn't pass muster. I explained that I had spilled some quantity onto my garage floor when I was replacing a headlight. At that point I must have passed some threshold of the "i-know-what-i'm-doing" home mechanic or the "complete-idiot" home mechanic. He was nice enough to stop the inquiry there and saved me a little face. So for $3.75 I left the store with a some power steering fluid and a small funnel to refill the reservoir.

So, in summary, this experience was an absolute unnecessary pain in the ass. I realized the folly of my plan about one-third into the debacle and kept thinking of reasons that I should just fold up now and waltz in to the nearest Oil Can Henry's to stop the suffering. Yet, I persisted and now I have two functional headlights in my car, and one extra piece of wire in my garage.

I'm installing DotNetNuke v4.7 and I scroll to the bottom of the standard page that I've seen many times before, when lo and behold, I come across this for all to see!

Everyone who installs a brand new version of DotNetNuke gets to see a tiny photo of me on the cover with Shaun Walker. Sweet!

I had remarked to The Wife that she had spent over N on clothes during the past month. She retorted that it couldn't be correct.

Thanks to http://www.wesabe.com, this was an easy thing to confirm. Wesabe organizes purchases that you upload to your Wesabe account from your bank. It creates some great charts and graphs for managing your money with precious little effort. All free of course.

I returned to The Wife and explained how all of the values are tagged correctly, and the value is actually N+1. There are purchases from Motherhood, Gap, Macy's and Old Navy.

And here's the quote:

"Oh, that's why! Not all of those are clothes. Macy's isn't clothes... it's make-up."

Zing!

In my experiences as a software developer, its fairly normal to hear comments like the following:

• That's too many hours
• They don't have the budget
• I'm not paid enough

I had the good fortune of attending a Portland XP Users Group presentation a few weeks ago by James Shore. He got off on a slight tangent and gave us (well, at least me) a simple equation to chew on:

He explained that at its core, Return On Investment is represented by the previous equation. It can help explain quite a bit about the world. This was in response to someone asking about the high cost of the software development methodology under discussion that night.

If you're presented with a scenario where the value is constant, then the only way to play the game is to minimize costs. Think of a job that never changes. If it always provides the same value to a business, management will seek ways to reduce cost in order to improve the ROI equation.

On the other hand, a scenario where value has the capability for growth is much more interesting. If you wanted to make $500,000 a year then you would be challenged to deliver some multiple of that cost as a value to the business.

Here's my favorite take-away: At some point along the graph, as value increases then cost becomes insignificant. This is the place to be.

The initial cost of software can make some people squeamish. I'm certainly not one to be afraid of zeros; I'm much more interested in the value.

• What is this solution doing for the business?
• Is there a practice in place for tracking ROI over time?
• How soon can it begin providing value?
• Can it provide even more value?
• It is possible to reduce cost and drive the equation even higher?

This is why I love my job at Pop Art. Driving value higher and then swooping back to cut costs with new technology that makes me more productive. Value will often come in several forms including cash value, brand value and community value. In any case, it all starts with that equation.

I was working with a web service client that talked to SharePoint this week. I wrote a quick Silverlight app that extracted a list of tasks out of a SharePoint list. I love how simple this is to tap into:

http://sharepoint.yourcompany.com/_vti_bin/lists.asmx

The previous URL will show the path to one of the web services provided out-of-the-box by SharePoint. This particular web service provides several methods for dealing with SharePoint lists. I just needed to call the GetListItems() method and pass in the list name and view name as parameters in order to get my data.

This worked fine on my local machine, but when I migrated the solution to a staging server, the SharePoint web service refused to send me the data. After a bit of finagling, I realized the web service was happy to talk to my laptop, but it politely declined the remote web server's request as I lacked the proper credentials. I even was running the web solution with impersonation enabled because I wanted to pass along my Windows credentials during the call from the web server to the remote SharePoint server. I forgot that this is just simply not possible.

For security reasons, the web server does not hold on to my credentials "just in case" I might want to use them later. In this scenario, I do need them - but no dice. This particular list in SharePoint is locked down tight.

I didn't have the proper credentials when my web service client fired off a request to SharePoint. When I was running on my local machine, using Casinni, my credentials were readily available. On a remote web server, the credentials vanish. This is called a "Double Hop" problem - the hops are from the browser, to the web server, to another remote web server. The second hop tanked. It was a silly mistake on my part, but hopefully by writing this down now will help me remember sooner next time.

The code below shows how I solve this problem by manufacturing a credential on-the-fly and then fire off a request to SharePoint. There are multiple ways of solving this problem; I just happened to chose this one.

         MySharePoint.Lists list = new ProjectBoard.MySharePoint.Lists();

         list.Credentials = new System.Net.NetworkCredential(

            ConfigurationManager.AppSettings["Credential.Username"],

            ConfigurationManager.AppSettings["Credential.Password"],

            ConfigurationManager.AppSettings["Credential.Domain"]);

         XmlNode listItemsNode = list.GetListItems(

            ConfigurationManager.AppSettings["LoremIpsum.Guid"], 

            ConfigurationManager.AppSettings["LoremIpsum.View.Guid"], 

            null, null, "100", null, null);

         XmlNode dataNode = listItemsNode.ChildNodes[1];

         foreach (XmlNode rowNode in dataNode.ChildNodes)

         {

           // extract values here

         }

Now that I've got this little prototype functional, I can encrypt the credentials in the web.config file by using DPAPI, an encryption tool that makes it easy to protect sensitive information. Since I'm creating new credentials here, I can avoid the Double Hop problem and get on with my prototype.