guffaw
Regarding my mention in the front page update from last week.
"SDA 2.0" was the site's big missed opportunity. The Cathedral model of a small team administering the site had many advantages, but the labour required to do it was unsustainable, and we all knew it. SDA 2 was based on the Bazaar model, in which we wanted to set up web interfaces to let the community do as much of the work as possible.
I had a carefully planned, working database schema (which handled all of the site's quirks as elegantly as possible) and had built a working read-only PHP prototype of the front end. I wrote scripts to scrape as much of the data from the old static HTML pages into the database as I could. This, at the very least, served reasonably well as test data for development. I posted the code for this prototype on the forum, sometime after I quit the site entirely. You should still be able to find it if you're interested. I had hoped somebody might pick up the work I did, but nobody bothered.
Here are the mistakes I made.
i) I wasted six months coding the intro video for PaX (while simultaneously still being responsible for site updates), when I should have been lobbying for and working on a site overhaul instead. This pushed my already-festering burnout to breaking point;
ii) nate wanted to migrate the whole site over to SDA 2 in one shot, so that one day the site would still be served from static HTML pages, and the next we would abruptly flip it over to the new database system, with all the data magically in place and ready to go. I always knew this wasn't going to happen with the constant influx of runs. My plan was to work on SDA 1.0 and 2.0 simultaneously, in such a way that we would slowly try to migrate stuff over bit-by-bit as new SDA 2 functionality was completed. If I had fought nate on this, we might have ended up retaining our position as the Internet's speed running nexus, but I didn't;
iii) persuading Radix to change anything fundamental about how the site worked was a struggle from day one, and added a needless political challenge to the technical ones.
Sites like speedrun.com and SRL had a couple of big advantages: They didn't have years' worth of legacy data to migrate, and they could develop their own sites at their leisure, while SDA still had to post updates day in and day out while simultaneously trying to work on upgrades.
That's the story.
"SDA 2.0" was the site's big missed opportunity. The Cathedral model of a small team administering the site had many advantages, but the labour required to do it was unsustainable, and we all knew it. SDA 2 was based on the Bazaar model, in which we wanted to set up web interfaces to let the community do as much of the work as possible.
I had a carefully planned, working database schema (which handled all of the site's quirks as elegantly as possible) and had built a working read-only PHP prototype of the front end. I wrote scripts to scrape as much of the data from the old static HTML pages into the database as I could. This, at the very least, served reasonably well as test data for development. I posted the code for this prototype on the forum, sometime after I quit the site entirely. You should still be able to find it if you're interested. I had hoped somebody might pick up the work I did, but nobody bothered.
Here are the mistakes I made.
i) I wasted six months coding the intro video for PaX (while simultaneously still being responsible for site updates), when I should have been lobbying for and working on a site overhaul instead. This pushed my already-festering burnout to breaking point;
ii) nate wanted to migrate the whole site over to SDA 2 in one shot, so that one day the site would still be served from static HTML pages, and the next we would abruptly flip it over to the new database system, with all the data magically in place and ready to go. I always knew this wasn't going to happen with the constant influx of runs. My plan was to work on SDA 1.0 and 2.0 simultaneously, in such a way that we would slowly try to migrate stuff over bit-by-bit as new SDA 2 functionality was completed. If I had fought nate on this, we might have ended up retaining our position as the Internet's speed running nexus, but I didn't;
iii) persuading Radix to change anything fundamental about how the site worked was a struggle from day one, and added a needless political challenge to the technical ones.
Sites like speedrun.com and SRL had a couple of big advantages: They didn't have years' worth of legacy data to migrate, and they could develop their own sites at their leisure, while SDA still had to post updates day in and day out while simultaneously trying to work on upgrades.
That's the story.
Thread title: