Originally Posted by
Tim in Hollywood
My wife and I both have CPs that expire 12/31/2012.
For quite a while, one of our accounts had the CP status bar (% toward qualification). The other account never had it.
Consider this another perk of RR 2.0.
It continues to amaze me that the web site is such a complete disaster. Though I will likely never know, I would love to know about the internal communication between the IT staff/contractor and management. Does upper management even realize what a complete boondoggle their site is now? They have to, right? Right?
In another life, I used to write code. Simple stuff actually. A little Pascal, a little technical BASIC and a whole lot of dBase. There comes a time in the evolution of a system that rewrites are the only viable method of fixing broken code. I do not think this has probably changed except that dynamic linking makes it even harder to do now that was when I was coding.
A complete rewrite is expensive, time consuming, fraught with danger. It is also seldom done. Patching code is fast and cheap. Patched code is often buggy. Poorly documented patched code is often not fixable.
I was taught to document every line of code, a process that often takes longer than writing the code. It saved me many, many hours in chasing problems. I would bet that the coding for the WN web site is highly patched and poorly documented. Or, they just do not care.
Sometimes a company will recognize the failure and will do a rewrite. I am sure you have seen it. Load up a retail site that you were familiar with and everything has changed. I mean everything. Done correctly it is faster, crisper, and more attractive. And you soon learn to use it because of intelligent designs. It is almost a work of art.
The WN web site is a chalk drawing on the sidewalk after a heavy dew.