2 ms·
I expect developers and sysadmins to work together on these things. I'm always confused when they don't, and saddened when people think that's okay. For instan
by generalk 16y ago
I expect developers and sysadmins to work together on these things. I'm always confused when they don't, and saddened when people think that's okay.
For instance: I wanted to do a few projects in Rails. I made sure that my admins had links, guides, and all the info they needed when I started the project. By the time I was ready to launch, they'd already had Ruby, Passenger, and all my dependent gems installed. Deploy was a breeze.
Later, a different coworker did a project in Django, but didn't breathe a word to our sysadmins. When he and the client agreed that it was launch time, our admins were scrambling to figure out what version of Python we needed, how to set up the environment, and what the deployment best practices were. Everyone was angry and the deploy was late, but the developer didn't see any consequences.
Kills me.
- dedward 16y agoI feel the same way. In the old-world way of things, the Architects of the system would take all of that into account - the sysadmins were just there to keep the systems up and running and install the software per the developers instructions. What's new, or seemingly new, because of the rapid advance of technology and the internet in general, is the rapid develop/deploy cycle, which ends up requiring a much tighter coupling between development and operations... the two almost blend together. The lines are getting fuzzy.