It was Monday morning. About a week ago. Tried to access the online version of the AJC. After much spinning of the wheel abject failure is acknowledged.
Probably because the morning update locked the editions list with a write semaphore which blocked the read necessary to allow access. Sloppy programming. But how can this happen? Well there is the rest of the story.
Check out the "Exception Details." Notice anything disturbing? That's right, they're not only using .Net, they have a Win32Exception. On a foundation of suboptimal technology they've managed to build a fragile application all but guaranteed to fail.
If you've actually read the AJC is there really any surprise?
Probably because the morning update locked the editions list with a write semaphore which blocked the read necessary to allow access. Sloppy programming. But how can this happen? Well there is the rest of the story.
Check out the "Exception Details." Notice anything disturbing? That's right, they're not only using .Net, they have a Win32Exception. On a foundation of suboptimal technology they've managed to build a fragile application all but guaranteed to fail.
If you've actually read the AJC is there really any surprise?