- Fix what's in front of you first, the rest you flick it into the future.
Example:
Project goes live with zero support team. It's ok, it's not your problem.
In fact celebrate going live gloriously. Nevermind that there's no support team and the maintenance contract was haphazardly negotiated.
Cause what's important is going live first.
The same goes with kicking off a project. Nothing is more important than having a project kicked off first with the CEO in attendance. You'll be seen as a do'er versus an excuse provide - If the shit is too complex, pretend you don't know about it. Never Ever be the one to raise it to the bosses.
The bosses probably know about it, but they need "plausible deniability"
In large organizations where the shit requires more than one party solve, nobody wants to pick it up. It's a given. Look away and cover your nose and just pretend you don't know as well.
And again, please practice in the mirror, when the shit does explode, just go. I'm really no aware how this can happen? No one from team ABC advise on the matter.
Hence why in any large project, always have a lot of people from alot of teams. Even if they don't do anything it's ok, cause at least they can be a scapegoat. - NEVER EVER RAISE THE SHIT
Have to repeat this again, cause when you do raise it, then it becomes your shit.
Not only that; you'll be seen as the person that comes up with problems rather than solutions.
CodeSOD: Plugin Acrobatics
15 hours ago