Implosion
2011 03 09
It looks like the rival department is carving up our shop. The big project I worked on a year and a half ago, which was killed by mis-management, has allegedly been put on hold indefinitely. Which is too bad, because I wrote the core logic & service framework for that project.
However, I don’t feel too bad, because a year before that project I wrote a tiny service that was so popular it killed the bigger project. That was an awesome project. It was a two-month project to wrap a client library in Java reflection and expose the service as an HTTP/JSON service. Groups loved it. In the first week of development, an important business partner came and said they wanted it. They started developing actively against it in the third week of development (!) and based their entire website re-design on top of it.
HA! My program wins! LOL!
However, the sad news is that I’ve heard development on that system is going to leave our shop, and move elsewhere. Does that mean they disband that team? I’d think so. That’s too bad. I really, really enjoyed working on that before Blow destroyed the team by putting a brain-dead minion in charge of it.
Right now, everything is quiet on our front. Our biggest business partner recently announced that they are going to standardize across all their affiliates on the product my new team produces. So that’s really, really good for me.
I’m just worried that my manager, who doesn’t necessarily like me, might look at the flood of people flowing off the other team as it disintegrates, and decide that keeping me around is less of a priority.
But I’m actually OK with whatever happens next. I actually think that industry salaries have zoomed past our corporate standard, and the next time I move, I’m going to get a good bump in pay.