I saw The Amazing Spiderman back in the late 70's, with a friend, both in our early 20s then. We went to an early showing. The theatre was packed, but we were the only ones older than 16 years of age in the theatre! Spot the nerds!!
There are enough recorded instances where the designers of software never foresaw it being used beyond a certain date, and put in mechanisms to automatically shut it down beyond a certain date, or not maintain it beyond that date, all causing problems. A better approach would be to email or message the system with periodical warnings to address the upgrade issues, irritating, but effective.
The problem is when management thinks that a whole lot of off the shelf products will solve the problem, where the real problem is that often there is little understanding of how to implement the procedures and process to effectively manage content and the SDLC.
Do I have to pay twice for viewing the same page on different days? What if I view the page on the day it is posted, a every day after that for a week to check the discussion? Do I get billed for 7 page hits? If so, this is not a fair method of accounting.
Just 28 days on complex software architecture? Wasn't it a chief MS software architect who recently said not to reengineer code because in the refining process there is too much chance of new bugs being introduced (because the code is not documented and the maintainer can never be to sure what exactly a piece of code may be addressing). The time line is crazy. In real terms it would be 10 to 20 times this for complex software. This is just the marketing department spin doctoring.
Slashdot Mirror
I saw The Amazing Spiderman back in the late 70's, with a friend, both in our early 20s then. We went to an early showing. The theatre was packed, but we were the only ones older than 16 years of age in the theatre! Spot the nerds!!
There are enough recorded instances where the designers of software never foresaw it being used beyond a certain date, and put in mechanisms to automatically shut it down beyond a certain date, or not maintain it beyond that date, all causing problems. A better approach would be to email or message the system with periodical warnings to address the upgrade issues, irritating, but effective.
The problem is when management thinks that a whole lot of off the shelf products will solve the problem, where the real problem is that often there is little understanding of how to implement the procedures and process to effectively manage content and the SDLC.
If you need multimedia and accessibility it's better supporting W3C initiatives like SMIL and SVG.
Do I have to pay twice for viewing the same page on different days? What if I view the page on the day it is posted, a every day after that for a week to check the discussion? Do I get billed for 7 page hits? If so, this is not a fair method of accounting.
Just 28 days on complex software architecture? Wasn't it a chief MS software architect who recently said not to reengineer code because in the refining process there is too much chance of new bugs being introduced (because the code is not documented and the maintainer can never be to sure what exactly a piece of code may be addressing). The time line is crazy. In real terms it would be 10 to 20 times this for complex software. This is just the marketing department spin doctoring.