open sourcing code will only take you so far:
http://iamseb.com/seb/2007/12/perl-on-rails-why-the-bbc-fails-at-the-internet/
"Whilst I applaud the technical achievement of the individual
developers, I deplore the situation that has forced them to do this."
Just to answer a couple of things in that blog entry...
Agreed we do have a strange and challenging infrastructure. Its highly
reliable because yes its mainly about publishing static files and ftping
them around the world. You could even apply this is very "web 1.0." I
still remember my shock almost 4 years ago when I learned that the XSL I
was writing could never be deployed dynamically like I was use to before.
Its frustrating for example that we have not been able to launch our new
website (yes remember those promises) for similar reasons but its not
really fair to just blame Siemens for all of this.
The BBC is changing and the likes of Backstage with our wild west
servers and audio and music with there own frameworks, we starting to
catch up with the sweeping changes which have happened. Stuff like
/programmes, blogs.bbc.co.uk and the Worldservice Bangladesh Boat API.
<http://backstage.bbc.co.uk/news/archives/2007/11/bangladesh_boat_1.html>would
never have happened a few years ago. At least not on bbc.co.uk.
There is a air of change going on as of late. I hope to have much more
examples to show in the very near future. Till then, feel free to rant
and rave about our infrastructure at the Christmas Party :)
Cheers
Ian Forrester
-
Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please
visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html.
Unofficial list archive: http://www.mail-archive.com/[email protected]/