Nothing makes developing an application buggier and slower than re-inventing everything from the ground-up.
Does the site seem slow and buggy to you?
Huh? What? But ... I didn't say anything about the site being slow: The "development" of this application (the nasty fan-site) is what I meant. Performance / speed of various features are more likely constrained by bandwidth / server load / network conditions than the underlying engine. NOT referring to the site as slow.
The "work" or "progress" or however you want to refer to it. Work on that is called "development". For things outside information technology, the word "design" might be the preferred word. The process of software / site / application "development" (the exact words I used were "developing an application") and that is the only thing I was referring to:
There is something like 20 years of technology that can be built-upon, saving time, and hassles which can be avoided with less time and effort wasted on troubleshooting bugs that shouldn't have been there, but were introduced because someone felt like they knew better than to rely on the work of others.
Basically, I worry when people implement CGI from scratch instead of using a ready-made (open source or otherwise) engine such as coldfusion, asp, c#, php, etc. etc. etc... Feels really gross to have issues like "how much memory should I set aside for this data-entry field" (password or otherwise) which wouldn't even be an issue otherwise -- We're going to have bugs that wouldn't have existed if things weren't done by hand with a manually implemented CGI. THAT will slow us down. Other bugs will exist because a readily available CGI engine or a library written or built for the same use, but then WASN'T used, in favor of "from scratch" etc. etc. etc.
