It takes 10 years?!?!?

Towards the end of the day today AP got into a conversation with TB and TO. The best part was when AP says, getting streamlined with the kinds of processes we’re trying to put into place takes 10 years or so. “We’re doing pretty good after only one.”

What a load of crap. It’s unlikely AP has ever worked anywhere for that long, or even worked anywhere that’s spent 10 years implementing a Change Management and source code control process. SInce a place that takes that long is unlikely to make it to 10 years.

I’ll be the first to agree that change takes time and that for us there’s a lot of culture changes that need to take place, but 10 years. What a load of crap.

Of course this comes from the guy with a contractor mentality to his work. Make it hard for anyone else to know what I’m doing to ensure I am impossible (perceived) to replace. He seems to thwart the process at every turn, doing CMs job for them, still doing release notes, not forcing them to call the developer on support that weekend, not making them call the teams who need to fix the problem, essentially hand holding the CM team on a daily basis.

Well he can keep doing it sinceĀ I have plenty of life I’d like to lead on the weekends, he can sacrifice his. I wonder if he thinks he’s still hourly?

3 thoughts on “It takes 10 years?!?!?

  1. Thomas Brock Post author

    That’s also the way most civil servants think. It ‘secures’ their empire…

    My immediate supervisor gets angry with me when I ask too many details of what he does…

    It’s one of the reasons why government business is done so poorly!

  2. Thomas Brock

    That's also the way most civil servants think. It 'secures' their empire…

    My immediate supervisor gets angry with me when I ask too many details of what he does…

    It's one of the reasons why government business is done so poorly!

Comments are closed.