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

BehaviorS.js - An alternative to Behaviour.js, event:Selectors and Low Pro libs for unobtrusive JavaScript programming

BehaviorS.js yet another unobtrusive JavaScript library similar to Behaviour.js and event:Selectors but in implementation uses hash based lookup without extending elements; so presumably it should be faster than the rest. The original script and idea was by JLof ; I extended it for DOMContentLoaded support, optimized a bit to avoid scanning of more depths, and added new rules support. I wanted to document the plug a long time and just got time to do it. For the time being BehaviorS.js is available here Update (2006-09-11) : Coralized the link to BehaviorS.js so as to save the load on free brinkster.com webpage Update (2006-09-27) : If the coralized link to BehaviorS.js doesn't work, use http://www21.brinkster.com/guideme/BehaviorS/ Update (2025-06-07) : Now available in https://github.com/rrjanbiah/behaviorsjs
17 comments
Read more

Save American College, Madurai

This post was written in 2008 and outdated now. For update, please check Save American College, Madurai (Update 2011) Update (2011-01-16) : Save American College, Madurai (Update 2011) I'm highly privileged to have 3 degrees (B.Sc. (Spl. Physics), PGDCA and MCA) from The American College, Madurai, South India . Unlike other "commercial" colleges, American College has given room for poor students and uplifted them. And unlike other "elite" colleges who'd give seat only for "intellectuals", American College has produced geniuses. In the recent months, the saddening thing is that the college is under divide (Principal Vs. Bishop). Here is the email I sent to alumnae lately informing about the informations that I received about the developments: Update (2011-01-16) : Save American College, Madurai (Update 2011) All: I was thinking that the " Save American College " campaign was a FUD . But, when I tried to understand the problem through my...
11 comments
Read more

Solved: "Ports" Tab Not Visible in VS Code (WSL2)

None of the solutions I found on Reddit or GitHub worked, and most of the related GitHub issues were locked. So I'm documenting this here for future reference. Problem When using WSL2 in Visual Studio Code, the Ports tab—needed to access your application in Windows browsers like Chrome or Edge—doesn't appear. Even the Ports-related options are missing from the Command Palette. Solution After a lot of trial and error, here's what worked: Run npx serve in the VS Code terminal. It will output a URL such as http://localhost:3000/ . Click the link (or use the Follow Link option). This will open the app in your default browser. You may notice that it opens on a different port (for example, http://localhost:64198 ). At this point, the Ports tab becomes available in VS Code. After this initial trigger, the Ports tab seems to remain available in future VS Code...
Post a Comment
Read more