"Just ask the Unix team", Not because it is their responsibility, but because they can solve the problem quickly as they have the widest berth of knowledge.
Coding as a Sys Admin is crucial. Just know when to say I can't(or won't), for your sanity.
This, a thousand times! I'm a UNIX Engineer for a large corporation, and I find that the UNIX team gets pulled into every problem, when the reality is, it is seldom an OS issue. It's because we have to have that depth of knowledge, just to set up a single box, never mind a fully automated HA environment. I find that we also have the job of calling out bullshitters who say "it's not our problem (I'm looking at you Network Team) or "no I didn't change anything!" (mister chmod -R 777).
On topic: Scripting is key to solving a lot of "run this on 300 AIX, 50 RHEL, 20 HP-UX, and 5 Solaris boxes" and staying sane doing it. Our problem is we have a ton of legacy scripts that do a lot of day-to-day stuff, which was great for 300 total boxes. On an enterprise level with thousands of machines, not so much. Now we're trying to replace a mess of scripts with enterprise level solutions, but figuring out how we do it now, and how we want to do it with some real software is more of a challenge than we thought. We're in a bit of a mess because someone automated everything with scripts, and it is not scaling.