posted on Aug, 28 2007 @ 02:09 PM
Good to hear that the board has evolved far away from its XMB roots SO.
XMB was recently taken over by a new group of developers and the last several releases have all been bug fixes to resolve serious exploits, even
though XMB is currently versioned 1.9.7 (and alot of the bugs and exploits in it were what you typicaly find in pre-V1 software).
Without knowing how and to what extend the database and code have evolved from their original roots, its hard to suggest anything other then the
obvious problems I witnessed.
Stuff like the subscriptions page, even though its probably not used often, is the kind of thing what can bring an otherwise streamlined and well
designed site, down on its knees, no matter what hardware you trow at it, just because it mixes in with the normal operations from time to time and
then causes things to go awry.
As they say, a chain is only as strong as its weakest link.
I myself would be considered a "server expert" too, but for me personally that means knowing and understanding the interaction between server and
its applications too.
I might not be able to develop software or web-apps from the ground up like software developers can, but I can read and write code perfectly, I'm
rather anal about OO development and adherence to standards and usually spot bugs and design flaws that the programmers themselves don't.
Also, I wonder if you ever thought about making a true redesign happen for ATS's website, instead of just evolving the site to new version levels.
The people that created Django for instance, they worked for a newspaper website where everything was running on PHP and because they found themselves
in an ever expanding flood of fixing bugs that creaped out of old parts of code, they did a load of research and eventually designed the Django Web
Framework (in python) to suit their needs and wants.
They crafted certain parts to interact with the old data in an entirely new way while developing completely new feature sets for everything else.
Doing something like this, off course would be a pretty massive undertaking, but doing it as sort of a side project until it reaches sufficient
maturity to replace the old platform could be best in the long run.
You can't keep patching and updating old foundations and design philosophies. At one point you have to set a vision of how you like to see things and
reinvent your application from scratch to meet that vision.