in reply to Re^4: best strategy
in thread best strategy

Everyone has to learn the first time.

True.

But doing it under the pressure of 6.3 I have been told by my Lead)(i have to make it and make it good else i would be kicked out :-)) is neither conducive to learning nor fair.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Replies are listed 'Best First'.
Re^6: best strategy
by Gavin (Archbishop) on Aug 25, 2008 at 17:36 UTC

    "I have been told by my Lead, I have to make it and make it good else I would be kicked out".

    Strikes me that you have been given an impossible task given your experience in Perl and the time frame you have been allotted.

    I have seen this before it's a management ploy to to give you a task that they know you stand very little chance of completing, so that you can be removed by default. Should you manage to complete the task next time you will be given an even more difficult one.

    I think I would be asking myself do I really want this job, do I need the pressure and hassle perhaps you should get out now.

    Good luck whatever, you've your work cut out.

      In the OP's situation I would certainly be getting my CV out. He can still talk positively about what he is attempting to do, and use it to help him find something better somewhere else.

      Tricky questions he can ask prospective future employers include

      • asking about the planning processes in the software development cycle,
      • what procedures and specification methods are used to ensure unambiguous communication to all team members,
      • how much time and thought is given to planning new projects or fixing poorly designed existing ones,
      • who has responsibility for all that,
      • who are the gurus in what areas,
      • what is the management structure and support like for the lesser programmers in the team
      • what training do new folk get in the company products and ways
      • what training do they get in key skill areas required for the project in hand
      ... and so on.

      Maybe they're why I don't get many job offers ;)