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)

Comments

Popular posts from this blog

Converting PSD with PHP/ImageMagick

After seeing feature rich options in Imagick PECL extension at Mikko Koppanen 's (the author) website and also impressed with ImageMagick 's features, I have decided to use it for the PSD to XHTML conversion website that I'm architecting and managing. Since, the team wants programming help for converting PSD images, I have tried it (documentation is sparse on PSD handling) Converting PSD to PNG/JPEG/etc Note that, flattenImages() is needed for layered/multi-page PSD file. <?php $im = new Imagick('test.psd'); $im->flattenImages(); $im->setImageFormat('png'); $im->writeImage('test.png'); ?> Extracting PSD layers One by one <?php $im = new Imagick('test.psd'); $im->setImageFormat('png'); for ($i = 0, $num_layers = $im->getNumberImages(); $i $im->setImageIndex($i); $im->writeImage('layer' . $i . '.png'); } ?> Note that, there is a better version below In a single call with writeIm...

The Overrated Tamil Culture

Since the COVID period, I developed an interest in exploring old books from the 1700s to the 1900s through Google Books. I first focused on the celebrated Protestant missionary Ringeltaube, but over time, my curiosity expanded toward understanding the demographics and social practices of that era. In Tamil Nadu, what is often celebrated as "Tamil Culture" revolves around the practice of monogamy, known locally as à®’à®°ுவனுக்கு à®’à®°ுத்தி — meaning one woman for one man. Some even compare this tradition with practices in other states, claiming Tamil culture is especially unique. This sense of pride is particularly strong around Madurai, where people often refer to themselves as “pure Tamil” when compared with neighboring regions like Kanyakumari, whose people they call Malayalis. What’s striking, though, is that this proud image doesn’t always align with historical accounts. A book published in 1885 (I’ve chosen not to mention its title or link to avoid stirring controversy) ma...

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...