Overloading at workplace

In every single company, the problem they face is that of job assignment to the employees. When i see some people coming early in the morning and leaving very late on one side, on the other i see totally jobless ppl.

Now let us just come down to SoftwareIndustry. I dont mind speaking about this cause, i am in one of them too. Though a company has ultimate expertise in “Object Oriented Principles”, they tend to get their concepts wrong everytime.
Lets consider these things to proceed further:

Company: WorkSpace
Vertical: Package
Project: Class (Architects/Designers: Interfaces)
Employee: Object (Project Manager: Public Object)

Now let me directly get down to the overloading concept which i have always wanted to explain.

Trainee Object: These guys only are “try-them-out” objects. If these objects dont prove their worth within 6 months they are never given any critical or important parts in the project. The biggest problem these objects face is the fact that, they may never be given job to prove their worth. Only if there is a lucky trainee-object will he get some great work to prove his worth. Every trainee object should be given equal amount of work and should be trained & not to sit idle.

Developer Object : These objects are created and never used for a real long time. Most of the time these objects are unused. But when the project gets into development phase, these objects are as good as dead. Their counterparts who are onsite do some similar kind of work but they are the rich cousins of the ofshore guys.

Any other Object: I preffer to keep my mouth shut cause i have no idea as to how hectic their work is.

Now coming to the point , “y did i post this nonsense in my blog?”


Cause i was totally jobless!!