Work

[legion]

As I've said a few times, I'm a year ahead of schedule on a project that is one year behnd schedule--I'm effectively two years ahead of the critical path on my project.

My project is divided into three releases. I've finished all of my work for release 1 and release 2. I just started work on release three a few weeks ago. I got an e-mail this morning explaining that all work on releases 2 and 3 is to be suspended immediately to concentrate on release 1. That's fine. That makes sense. Even though I'm ahead of schedule I do have to constantly talk to teams that are behind schedule to move my work forward. The bottom line is that I can continue working but I can't bother other teams who need to concentrate on release 1. Eventually I will hit a point where I can't move that work forward without bothering the behind-schedule teams. I actually hit that point this morning shortly after getting the e-mail.

To give you an idea, on one of my programs (my release 2 stuff), I wrote 12,000 lines of code that is now tested and ready to go. Another team of 20 people is responsible for writing the remaining 2,000 lines of code to make it all work and it has taken them MUCH longer to write much simpler code. I have three such programs and two are done. I can get work done very fast with a minimum of mistakes--mostly because I know what kinds of questions to ask upfront to avoid expensive rework later. Release 1 stuff has all work done and is ready to go.

I just got a second e-mail stating that Saturdays are now mandatory work days--no exceptions (except project managment, of course)--until the project is back on schedule. That's right, I'm supposed to come in on Saturday, but I'm not allowed to work on anything that I have outstanding. I can't even pitch in and help other teams. Other development is being done in Java and COBOL. I don't know Java or COBOL. I don't have the tools to work in Java or COBOL. So I'm supposed to come in on Saturday and do nothing because managment is unwilling to identify the teams that need to be there and the ones that would just get in the way. Nope, instead they will punish everyone because some teams aren't getting their work done on time.

[onewhippedpuppy]

"Peter, sounds like you've missing a lot of work lately".

"I wouldn't say I've been missing it Bob".

[m21sniper]

Originally Posted by legion

As I've said a few times, I'm a year ahead of schedule on a project that is two years behnd schedule--I'm effectively two years ahead of the critical path on my project.

My project is divided into three releases. I've finished all of my work for release 1 and release 2. I just started work on release three a few weeks ago. I got an e-mail this morning explaining that all work on releases 2 and 3 is to be suspended immediately to concentrate on release 1. That's fine. That makes sense. Even though I'm ahead of schedule I do have to constantly talk to teams that are behind schedule to move my work forward. The bottom line is that I can continue working but I can't bother other teams who need to concentrate on release 1. Eventually I will hit a point where I can't move that work forward without bothering the behind-schedule teams. I actually hit that point this morning shortly after getting the e-mail.

To give you an idea, on one of my programs (my release 2 stuff), I wrote 12,000 lines of code that is now tested and ready to go. Another team of 20 people is responsible for writing the remaining 2,000 lines of code to make it all work and it has taken them MUCH longer to write much simpler code. I have three such programs and two are done. I can get work done very fast with a minimum of mistakes--mostly because I know what kinds of questions to ask upfront to avoid expensive rework later. Release 1 stuff has all work done and is ready to go.

I just got a second e-mail stating that Saturdays are now mandatory work days--no exceptions (except project managment, of course)--until the project is back on schedule. That's right, I'm supposed to come in on Saturday, but I'm not allowed to work on anything that I have outstanding. I can't even pitch in and help other teams. Other development is being done in Java and COBOL. I don't know Java or COBOL. I don't have the tools to work in Java or COBOL. So I'm supposed to come in on Saturday and do nothing because managment is unwilling to identify the teams that need to be there and the ones that would just get in the way. Nope, instead they will punish everyone because some teams aren't getting their work done on time.

Play WoW all day on saturdays.

[Dantilla]

I'll have to check "Off-Topic" more often on Saturdays to get your latest thoughts.

[masraum]

Nice! Have you explained this to your manager, or maybe just send him the link to this thread.

Frustrating, isn't it. You're apparently working too hard. You're going to make the others look bad and then they'll have it out for you. You'll get fired for being too good. So, learn to slack more and you'll be happier and have more job security.

[Rikao4]

Static could use Sat. off..
sit in for him ...you get to send folks to the Island..
granted your at work..but the power

Rika

[legion]

Originally Posted by masraum

Nice! Have you explained this to your manager, or maybe just send him the link to this thread.

Frustrating, isn't it. You're apparently working too hard. You're going to make the others look bad and then they'll have it out for you. You'll get fired for being too good. So, learn to slack more and you'll be happier and have more job security.

Look at my post count.

I don't work hard, I work smart.

I have a talent for sniffing out issues very early on that usually don't seem to be discovered until design, or coding, or testing. I'm very good at learning from my mistakes and avoiding the same kinds of problems twice. I think some people hate working with me because I force them to address issues when they just want blind signoff on requirements so they can move on (and leave the problems for me to deal with later).

I don't write code faster than other people. I tend to write a lot of tools to automate tedious tasks and testing. On my last big program, I could execute and record the results of about three unit test cases a minute because of automation. Most other analysts seem to execute one test case every five or ten minutes. It was taking me less "work" to execute dozens of test cases that it took other people execute one. Once again, because of technology differences, the tools I wrote couldn't be used by other people.

[legion]

Originally Posted by masraum

Nice! Have you explained this to your manager, or maybe just send him the link to this thread.

I'll talk to him tomorrow. I was in a different building for meetings when the second e-mail hit. He was on the e-mail too. I'd actually be pretty surprised if he hasn't "addressed" this already. I like my manager. He strikes a good balance between anticipating issues and leaving me alone to get work done.

[jyl]

I can see some possible outcomes.

1. You don't have to work Saturdays.

2. You get assigned to a different project in addition to your current one, and don't have to work Saturdays.

3. You get assigned to a different project in addition to your current one, and do have to work Saturdays.

4. You are laid off effective immediately, since your services will not be needed for 2 years.

Just kidding about #4, I think. Anyway, plan to push for the outcome you want to get . . .

[vmisquez]

You should not be punished for the schedule slip since your code is already done. But I would worry about the new code being hacked-up on the weekend. Make sure your code still plugs-in or else you will be the one holding the schedule back.

With your talent I would just find another job. Surround yourself with talented competent developers and you will feel energized.

[legion]

There's not a whole lot of risk that they can mess up the interfaces with my stuff. It's not impossible, but it's unlikely. My stuff is a background process that is pretty loosely coupled with the rest of the code with a standard interface. I wouldn't mind being on call to address actual problems. I do dislike being ordered in to the office with no actual work.

John, I'm pulling for #2. I've been telling my manager that I would run out of work for awhile. His response so far was that he needed to keep me around and ready to fix any problems that might arise because my project is the number one priority for my department right now. Essentially have two thirds of possible sources of work eliminated for the time-being will give me more pull with getting assigned to something else.

[KFC911]

Chris, a few folks have "it" when it comes to IT and it comes so naturally it's pathetically easy. In the real world (from my experience), "most" don't and that's just the way it is in out there in "corporate land". I don't know what to tell ya, but don't let it get you down...it "is what it is". Might be time to pursue other endeavors...it doesn't get better as your career progresses, just more and more frustrating. Good luck, and in the meantime, just "play the game" and don't let it get you down.

[Aurel]

Maybe you are too smart for your position and need to find a more challenging one.

[Dave L]

Kind of a dicey time to look for a new job but perhaps you could make yourself more valuable by learning Java or another language. At the very least it would keep you busy.

[legion]

I like my employer. There are plenty of opportunities in my department. I'm just "locked in" to my current project.

It's time for a conversation with my manager.

[jyl]

Good point above about using this as an opportunity to learn new skills. After all, you probably won't stay there forever and having lots of skills and experience on the CV is always a good thing.

[Schumi]

I had a job in an IT department once that maintained about 1500 systems in 4 different buildings in two towns. I was responsible for a month long project which required me to service about 1000 machines, wiping the drives on a lot of them, cloning them, and testing them. Also, this involved cleaning the fans and ensuring everything was in working order.

I had a hard drive clone machine that would format the drives and install the necessary software, depending on the machine and what it was used for, to where I just swapped some plugs and hit a button. I had 4 weeks, 8 hours a day 9-5 to do this job. I worked my ass off the first week and then projected out hte project and realized I would be done with everything sometime near the end of the second week.

I opted to stretch that job out over the entire month. I would go into a lab with about 30 machines, sit and slowly let each one format one at a time while I took another apart, all while watching DVD's like Superbad on the built in LCD projectors or on Smart boards. I was the only one in the buildings at these times except for some custodial staff possibly, so I didn't give a sh&%.

At the end of the day (month), the boss was happy, I was happy, and it was overall a pretty good way to spend my time. Would I have liked doing something a bit more involved? Sure, but that wasn't going to happen as the two jokers running this operation were not the smartest IT guys in the world, and I could have easily ran circles around them.

Legion it sounds like you got the sh*% end of a stick and are stuck because of other people not being as good at their job as they could/should be. Looks like you should be moving up to management and getting payed a good amount more if you know how to manage your part of the project that well.

[jyl]

I wrote my 2009 plan tonight (something we do at the end of each year, what went right/wrong last year and what we want to do this year) and I'm going to try and find a new sector to work on. Maybe financials.

[legion]

Originally Posted by Schumi

Legion it sounds like you got the sh*% end of a stick and are stuck because of other people not being as good at their job as they could/should be. Looks like you should be moving up to management and getting payed a good amount more if you know how to manage your part of the project that well.

It's something I'd like to do eventually. I have two things I'd have to work on first. I'm not good at dealing with people who aren't self-motivated, and I need to be a little more patient when things don't "click" when I'm explaining things to people.

The project I'm on has dozens of very talented people on it. I'm not at the top of that list. The problem is that there are also close to a thousand people on the project. It's a HUGE undertaking. Problems tend to ripple. A small problem in one area often causes a huge problem in another area. I've been fortunate in that I work on some isolated stuff. It's also been pretty low profile because we're not the squeaky wheel.

I'm mostly just pissed about the Saturday thing and venting about that. I don't mind having to work extra to make a deadline. I do hate having to come in on my own time not to work.

[911Rob]

sorry, I couldn't do it. I'd be outa there soooo fast.
life's too short to be bored, sitting behind a desk for no bloody reason!

What feels better to you?
1. stay where you are
2. move on to something else

do what feels better to you imo.