Too much information?

Spent a good part of the day with Rick, watching him install a new release of the system. Interesting, but it was all Database Administrator (DBA) work; in fact, a lot of the activities he performs are DBA functions. I really wonder if his Charlotte manager understands everything he's doing - a DBA/developer, a dual skill set, is needed to fill the job as it now exists.

I sent his boss an e-mail to see if I could clear this up. Will it continue to be a dual skill set position, or primarily a developer role, with the DBA functions going back to the DBA team. An important point: if the former, I lack the background the position demands.

More scuttlebutt: Susan, his co-worker that's a business analyst on the team, is being yanked off the team (not of her choice). She mentioned there's a lot of new projects coming down the pike, but who's going to do them? With Rick's technical knowledge walking out the door, and Susan's business knowledge leaving, it's going to be a lot harder for a new guy to get up to speed. Meanwhile, a group of "high maintenance" traders are just about to roll on the system and will probably besiege the team with urgent questions.

The dreaded "O-word" was also being floated about this position. If the manager does decide to make this a traditional developer opening, what's to keep it from being outsourced to our India compatriots? In fact, this manager has another team under her consisting of 14 India developers.

Relative safety, ironically, was one of the attractive points about this position. Even though it was ugly technology, maybe it would be a safe haven for awhile.

Hopefully the picture will get clearer next week. But this week, after starting on a good note, has not ended on one.

Technorati Tags: layoffs, outsourcing