Taking Responsibilites too early - danger or boon?

Posted by narresh on Stack Overflow See other posts from Stack Overflow or by narresh
Published on 2009-08-19T05:54:40Z Indexed on 2010/05/29 21:02 UTC
Read the original article Hit count: 276

Filed under:

Just I am only six months experienced guy in software industry.Due to recession season,a large volume of employees from our company are asked to leave.This impact affects the new inexperienced guys.
The problem is

  1. We have to interact with the client directly to gather the requirement

  2. We have to design all HLD and LLD ,use cases and DB Diagrams ,that should staisfy the customers who keeping the high software insdutry standards

  3. In this do or die situation (Client gives us narrow dead line),we spend most of time with interacting client (only less time is available for development and testing,even sit out for 24 X 7 won't help us to finish our task)

  4. If task will not be finished with in the expected time frame ,that will trigger poor performance ration to our profile


There are two important questions flashing in our mind : (1) Quit the job and do other business
(2) Face the challenge : (if the option is to face the challenge ,What are all the tools should we follow to automate requirement gathering,testing,DB diagram,Code review and the rest.(We are working on ASP.NET 3.5 with SQL Server 2005).


© Stack Overflow or respective owner

Related posts about career-development