Skip to main content

180+ seconds loading site - how to fix [sic]


I came across a site that has a loading time of 180+seconds. When discussing about how to fix such sites, a person who has steep corporate culture/experience, informed these notes. Very interesting...

Politics... Politics...
Create more and more politics. Create politics on URLs, labels, design and any weird things. Also, create mad/unnecessary competition--competition without any excellence.

Hype... Hype...
Create fake hype around the crap site. Make everyone speaks about it.

Team building = poaching!
Look for good performers in other team and poach them. Break other team through sneaky attempts. Get help of cabals.

Factoid... Factoid...
Spread rumors and factoids about other teams.

Appraisals... Appraisals...
Recommend more and more appraisals for sycophants.

Flexibility... Flexibility...
Treat sycophants like scientists and throw them with flexible timings. Still defend them so that you'll also be praised.

Time++ Time++
Develop the project for 13+ months; remember 13 is a lucky number. Still throw more and more time.

Vengeance... Vengeance...
When smart people question about performance of the site, take vengeance and fire them with smile.

Cartoonish rainbow web designs
Keep kids and sycophants around so that they'll always "appreciate" cartoonish designs. Kill readability and visibility with multiple colors. (Read Steve Jobs' take on ESPN phone)
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

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

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