On Fri, 2012-08-31 at 11:49 -0700, Nathan Hruby wrote: > On Fri, Aug 31, 2012 at 11:27 AM, Dan Ritter <d...@randomstring.org> wrote: > > On Fri, Aug 31, 2012 at 02:03:36PM -0400, Adam Tauno Williams wrote: > >> Ditto, this is the life of the System Administrator: here is the box, > >> here is the application, go... After doing this for 20+ years the > >> sermons about proper development and design techniques get tired; it > >> may all be true, but it doesn't address the facts on the ground. And > >> developers do not listen to System Administrators, what would we know? > > Then you have a dysfunctional organization, and you should work > > to fix it or move on to some place better. > > To give you hope: at my workplace, sysadmins are routinely > > consulted by developers about hardware, performance, and general > > requirements in advance of changes. > Easy to say, not so easy to do. A lot of what Adam talks about is a > cultural issue that takes time, energy, politics, perseverance to > change. > System Administration ain't just routers and CPUs.
In-house developers are one thing - but what about 'off-the-shelf' applications, vertical proprietary applications, etc... often you can't talk to the developers, and those developers there are often out-sourced from somewhere else. The provenance of real-world code can be quite involved and legally obscured. When management says "we've decided to run XYZ". You can push to get things changes, but in the interim it is the admins job to make it go.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
