Problem is when you fix other folks mistakes code-wise, you become the programer / maintainer of that overnight.
So being pro-active and showing initiative will actually backstab you later on
This is especially true for large-scale deployments and implementation.
My story is that my company implemented (bought) a completely new core solution.
There were, of course, alot of issues and bugs software wise.
But the unix part was working fine most of the time, so system folks like myself were helping business IT (app folks) to realize what's wrong by doing tcpdumps, AWR's.
At the end unix folks were explaning core bussiness to folks who should know it.
And nowadays (we are in production), i still get phone calls from folks who need their part explained.
That why in the past year or so i avoid being everything else except what i'm paid for.
It should be an advantage to know what's actually going on business-wise, but practice has showed otherwise.