Skip to main content

Work avoiders on the rise

roughly 80% of the effects come from 20% of the causes
-- 80–20 rule / Pareto principle
One popular store (that is known for its less selling price, 6-storied air-conditioned showroom) is situated to close to our home. But, Heleena is allergic to it. Reason? Even though there are at least 50 sales people per floor, only 1 or 2 people will be working and responding to the customers' queries.

In another shop, I even noticed that the owner was serving customer when many staffs were cleverly avoiding the show! I'm finding the same problem everywhere. Who're affected here? Obviously the people who're actually working--they will have to handle more work that the clever people have avoided.

Two common gestures/characteristics I have noted in these clever people: 1. They'll pretend to be absolute ignorant (These people's agenda are merely to avoid works, but not to take credits.), 2. They'll create politics on anything (These people's agenda are to take credits without working. These people will usually be more shrewd and talkative.).

While I don't have any solution, I think, over the period of time, everyone will get smarter and will start avoiding works.

Labels:

Comments

Post a Comment

Popular posts from this blog

Open source PHP frameworks and problems

I was using CakePHP for sometime and proposed CakePlus , another UIMS toolkit on the top of CakePHP but also altering some problematic core of it. The thread should explain the outcome of the post. And, then I noted Akelos framework has most of the things built in. Issues with frameworks esp. CakePHP Scalability not a priority - Developers aren't aware that we can't throw more and more hardware Excessive use of regular expressions Evangelist isn't aware that the framework throws many queries unnecessarily More memory consumption - 100M would never be enough for a simple project Poor coding standards and practices - Prolong use of extract() often leads to more memory consumption Can't use the native approaches or baked codes. The override approach always lead to hard to debug codes Poor architected codes and no clear defined approaches. People belong to the cult drives the direction and often throws unprofiled codes. No native provision to share codes between M-V-C and...
6 comments
Read more

What's wrong with delicious.com?

The recent UI changes of delicious.com is quite confusing and smells suicidal phase. I have noted that, after Joshua Schachter sold it to Yahoo!, it's going crazy changes. Probably, it's because a Yahoo! company now or Engineers don't get the real idea? Some crazy moves: del.icio.us to delicious.com change; probably to reach countries that censor .us TLD? delicious.com to www.delicious.com; unjustified Perl to PHP switch; why? for:handle geekish way to share to separate box; crazy but ok. Looks like, the new Yahoo! guys don't know how to make it a cult following like how twitter popularized @handle Recent broken UI
Post a Comment
Read more

Interview question #2

This is related to PHP's array . An array has number of elements. All elements are integers and unique, which means there is no repetitive integers. (e.g.) $foo = array(7, 5, 9, 13, 2, 8); You have to sort the array, provided: You should scan the elements only once. You're not allowed to compare the elements when sorting. (i.e., you're not supposed to use any comparison operators) Sorted resultant array may not be the source array. How will you do that?
6 comments
Read more