Dan Tappin wrote: > To be honest the real answer will be unpopular but since the old system > is unusable, not maintainable it should be replaced. I think if you > estimated the time / cost to rebuild the system from scratch it would > still be the better than trying to continue with this PITA system. > > Why don't you at least start on a new UI from this point and show the > company the benefits and then work on replacing the old UI? > > I think holding on to the old way of doing things just because so much > time was put into it is perhaps a short term solution. I agree with you 100% in principle. I failed to mention this, however: I now work for the "Institute of Design" a graduate school for product Design of the "Illinois Institute of Technology" The front-end of the site was "Designed" by a committee of faculty. The back-end was designed by my boss the IT/faculty guy, and by a first-year graduate student who means well, and is really nice and all that, but... I've only been here a couple months. They still believe the code-base of my predecessor is GREAT. Let's just say it would be work-political suicide to suggest starting over at this point. And I *do* need a job right now. On the "plus" side, minimalism is "in" now, so the front-end is actually not so bad, for the most part. And my boss is anti-JavaScript, anti-Flash, and even anti-Cookie (well, he's not, but he knows too many users are) so a lot of Good Things are involved here. Even the back end isn't *BAD* except for trying to make it too much like a desktop application, which didn't seem to bother my predecessor and his zillion temp tables. PS Y'all take this CEO thang way too seriously :-) It's a JOKE! -- Like Music? http://l-i-e.com/artists.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
