Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
Perl

Submission + - BBC creates 'Perl on Rails' 2

Bogtha writes: Long-time users of Perl for their public websites, and having successfully used Ruby on Rails for internal websites, the BBC have fused the two by creating a 'Perl on Rails' that has the advantages of rapid development that Rails brings, while performing well enough to be used for the Beeb's high-traffic public websites. This is already powering one of their websites, and is set to be used in the controversial iPlayer project as well.
Games

On the Moral Consequences of Gaming 170

N'Gai Croal and the LevelUp blog are collaborating with the popular UK games magazine Edge, and late last month we discussed the emotional impact of games. Or, more realistically, the lack thereof. This week N'Gai has been exploring what could be done to reinforce that emotional impact, and perhaps take those choices to a moral level. "What if developers attempted to bring social sanction into the experience? What if your Gamertag were designated 'Child Killer' for having murdered [Bioshock's] Little Sisters--or 'Good Samaritan' for having saved them? Microsoft recently announced its plans to add the Facebook and MySpace-inspired feature of allowing you to browse your friends' Friends Lists; what if everyone on your Friends List were notified each time you killed a Little Sister--or every time you rescued one--like the Status Updates on Facebook?"

Comment Security (Score 1) 152

From a security standpoint, developers should not deploy, install, manage, or administer any production servers. It is a conflict of interests and is covered by separation of duties.

That being said, I've worked in many environments. In my current position we have four teams.

1) Development
2) System Administrators
3) Application Administrators
4) Database Administrators

Development develops the applications, System administrators manage and maintain the hardware/os, app admins manage and maintain the applications, and the dbas manage and maintain the databases.

    Development writes the applications and hands them off to the application administrators. These guys install the app in our QA environment and go through some testing. Once it's tested internally, we install it in UAT and give our customers a chance to test. If there are any problems during testing, the release goes back to development. Once everything has tested clean, we have a change control meeting with the DBAs, App admins, and System admins to discuss all of the moving parts and work together to put everything into production.

I think we have the best of both worlds. Development is out of the loop after they hand off the product, but we also have Application support folks which work closely with development and know the applications and their requirements.

Slashdot Top Deals

If God is perfect, why did He create discontinuous functions?

Working...