Category: gzCope

insufficient communications about slipp timelines

Posted on by tiger40490

More than one GS project manager told me 1) my communication wasn’t enough and 2) my project management can improve.

I explained that i always inform PM whenever there’s a timeline slip. Separately, these 2 project managers gave similar answers. They both said I did inform them frequently about timeline slip, but such communication is neither enough or effective. PM can’t do much with that information. PM absolutely needs to know the reasons and the solutions.

Looking back, i believe i always gave my full analysis including the reasons or solutions i know. 知无不言, 言无不尽. What they need and expect from me is beyond my abilities. Dad said i already gave my best shots.

Maybe they expected me to find out from colleagues the reasons/solutions and report to PM.

I think GS managers simply expected more. They expect every team member to be as effective as the top performer. Making the “acceptable” effort is not enough. Do everything you can to get things done as fast as you can. If a colleague can do a bit more in this context, then you should too.

I guess these PM really want to get to the bottom — either you admit you are technically incompetent, or you are blocked by some external factor including a technical issue no one can resolve. As Lance (lab49) put it, clarity is everything.

cost/benefit analysis of copy paste coding

Posted on by tiger40490
In other projects, the priorities could be different, but in my project, top priorities are
#: Can boss tolerate such copy-paste? yes
#: how much time is given for this project? enough for A or B.
#: [A] even if you have enough time, should u spend the extra time here or on other areas?
#: [A] regression test effort

#: [A] integration test effort

#: [A] readability
#: effort during subsequent code changes — Just copy the changes over into the new sp
Change is frequent. future changes by other people may disfigure your design.
Plan A: copy paste the common code blocks into a self-contained new sproc.
Plan B: modify existing sproc to call a new sproc, so as to avoid copy-paste.
Considering all the priorities, the cost-benefit of Plan B is questionable.