(Error 0x80090022) tattoos, I'm buying
(Error 0x80090022) For customized troubleshooting information for this connection, click Help. Thanks. That was really helpful. I was just reflecting on how much better my life would be if I could just have my own 0x80090022 to care for. As a user, don't you just gnash your teeth with this kind of stuff? As engineers we've got to realize that no normal user, upon seeing HRESULTs in error messages, ever whacks their forehead and says: "Oh! Right! The old (Error 0x80090022) silent context acquisition gag. Of course. I remember that one."
I agree 100% with Scot on this one. If there are any people out there reading my blog who manage development teams, you need to read this entry in full; then once you've read it, you need to allocate enough time in your project plan to have someone other than a developer (PM, BA, QA resource) to write up the text of all these error messages.
Of course as developers, we have to do our part; and a big portion of that is to use resource files for the error message text. You should try to never compile down an error message into your code. Set up a strategy for how you will handle and present error messages early in the game. Very often this is overlooked until the last minute and can prove to be a real pain late in the schedule if not handle soon enough.
So how do I know all this? Because early on in my last development effort, we didn't set up any type of strategy, so by the time we hit UAT, we had error messages popping up from 8 different developers, all written differently (most having less than 5 words), and people were wanting them changed. Ugghhhh.... The next one will not be that way!
[Listening to: Assimilate - Skinny Puppy - (06:58)]