Archive for the 'Work' Category

No, There’s Nothing New to See Yet!

So much of what we call management consists in making it difficult for people to work.
- Peter Drucker

Boy, isn’t it the truth? My boss is “managing” me right into a hole of utter un-productivity right now.

He apparently doesn’t understand that only 10% of the project is actually the layout of the interface (ie: stuff he can “see”). The other 90% is where you’re working in the background making sure that pretty interface actually does something.

Two to three times a day, he’ll come by, call me, or email me asking if there’s anything new for him to see1.

No, there’s nothing new for you to see, I’ll tell you when I’m done with something so you can see it. The more time we spend talking about how there’s nothing for you to see, the less time I get to spend actually working on something for you to see.

Add to it that it reinforces a bitter feeling that I’m not getting anything done nearly fast enough even though I’m working my ass off, and you’ve got one thoroughly unhappy developer.

Time to call those two job recruiters back, me thinks…

  1. He’s supposedly on vacation this week, but at 8:24 this morning he still found the time to email me asking if there’s anything else he can see. [back]

Worst. Organized. Project. Evar.

For the last two weeks, I’ve been working to design a one-off enrollment system1 for a client, and it seems like it’s just been one road-block after another.

First, their data was incorrect. And then again. And for good measure, a third time. To be fair, I don’t know if it was their fault or ours the second and third time (mis-communication somewhere about what translations we were making), but the first time certainly was2.

Then, there’s the fact that when I notified the person in charge of coordinating this data exchange with the client, they apparently “missed” the email… And so three days later I’m asking them where the hell my answers are, and they have no clue what I’m talking about.

Next, apparently no one really knows what data the client wants to get back from us for entry into their system. On some things, they claim to want all coverages. For others, just changes. Then there’s this one piece of information they don’t seem to have thought about nor want at all…

Finally, 4 days before the system is to go live and we’ll have thousands of people from across the country calling in to enroll using it, as I’m working my ass off to correct a few bugs and get final testing in, I notice that the spreadsheet I originally got says that the client is expecting data back for a coverage we’re not supposed to be enrolling them.

Uhh, what? How can we give them back data on something we’re not enrolling? Back to the project manager we go… “Oh, right… That spreadsheet is old, I’ll see if I can find a new version for you.”

WTF? 4 days from live and I’m the one that has to realize no one bothered to give the programmer the real specs? If these were freelance clients, I’d never work for them again… Alas, they’re internal company employees and I’m not their manager…

  1. We do health insurance claims-related stuff. [back]
  2. They duplicated first_name in the last_name field of the data file they sent us. [back]

It’s a Beautiful Thing


chris@FRANK:~$ uptime
22:25:03 up 393 days, 3:19, 1 user, load average: 0.08, 0.02, 0.01

Sometimes there just aren’t words to describe certain things…

Missing NCIS Tonight

I totally missed NCIS tonight. I didn’t actually get home from work until after 7:00, so my evening was really thrown off-kilter as it was. Somehow, I just relaxed on the couch watching some old Remington Steele DVDs and totally missed it when 8:00 rolled around.

Don’t you love it the week before a vacation, when you’re running yourself even more ragged than usual trying to make sure everything’s ready so you can waste a week trying to relax? Ugh…

Someone please tell me that tonight’s episode was a re-run. Anybody?

Asking Too Many Questions

Found this little nugget of gold at the end of Junior programmers: Earn Respect in 5 Easy Payments (+$19.95 P&H):

It is perfectly acceptable to ask questions of people on your team, even if you are ’senior’ or leading the team. The one trait that is hated from a junior team-member is asking too many questions. This trait is not all that common but when it is encountered it is probably the most annoying problem to have in the office. Only ask a question when you have spent a reasonable amount of time (say at least 15 minutes) trying to find the answer yourself - go through the sourc-code, search the documentation, Google it. Only when you are completely stuck should you get some help.

So many times I have been asked something like “what does this message mean” and I have found the answer on the very first hit of Googling that particular error message. This is embarrassing for the question-asker and annoying for me because I was distracted for an easily found answer.

How true it is. This is a horrible problem at our office. Because we have “lax standards” (yes, I’m being very nice here), there are a number of people around on a daily basis that either don’t have the mental capacity to actually figure out a problem as it pertains to their job description, or who are simply too lazy to figure it out on their own.

As a result, those few who actually do posses that kind of common-sense reasoning ability get “dumped on”. Sure, maybe I could figure this out on my own, but why bother? Chris is right across the room! He’ll be able to tell me what I screwed up, even if it doesn’t actually have anything to do with his job!

He didn’t write that reports program and he’s used it twice in his entire career, but I can ask him anyway!

Now to be fair, I’m not sure if this reflects more poorly on their manager for not firing incompetent employees, or on mine for not telling people in no uncertain terms to take a hike… Either way, I’m the one that ends up suffering because “management” isn’t doing their jobs appropriately in one form or another.

Beware all ye who enter unto the Systems department today…