| Subcribe via RSS
Most office workers find computer jargon as difficult to understand as a foreign language, a survey suggests.
Three quarters of workers waste more than an hour a week deciphering what a technical term means, the poll found.
Terms such as jpeg, javascript and cookies are among the problem words highlighted by firm Computer People.
Get the hell out of here, an hour a week! Please. Here let me show you something, Google: “define:bullshit”.
Tags: BBC, GoogleKevin Sites in the Hot Zone From Yahoo! News
Yahoo starts reporting.
One of the world’s most respected war correspondents, Kevin Sites has spent the past five years covering global war and disaster for several national TV networks. Now he joins Yahoo! News to provide a unique, multimedia perspective on some of the world’s most troubled and dangerous places.
This is the same dude who ignited a firestorm for reporting the killing of an unarmed Iraqi in Fallujah by an American soldier.
When Yahoo isn’t assisting in the persecution of political dissidents in China it seems they are breaking new ground in news reporting it seems.
The Kevin Sites Blog has some interesting bytes.
Tags: Kevin Sites, Kevin Sites Blog, Yahoo!Undeniable evidence that Pirates Are Cool:
As a correlary, this also can be attributed to a decline in grog consumption.
And as we all know, grog contains one or more of the following:
Shortly after Hurricane Katrina roared through South Mississippi knocking out electricity and communication systems, the White House ordered power restored to a pipeline that sends fuel to the Northeast.
That order - to restart two power substations in Collins that serve Colonial Pipeline Co. - delayed efforts by at least 24 hours to restore power to two rural hospitals and a number of water systems in the Pine Belt.
Good to know we have our priorities straight.
Tags: Colonial Pipeline Co., communication systems, electricity, Hurricane Katrina, water systems, White HouseSun’s, allegedly, rejected print adverts for their Sun Fire series.
Tags: Dell Sucks Sun Microsystemsn the interests of creating employment opportunities in the Java programming field, I am passing on these tips from the masters on how to write code that is so difficult to maintain, that the people who come after you will take years to make even the simplest changes. Further, if you follow all these rules religiously, you will even guarantee yourself a lifetime of employment, since no one but you has a hope in hell of maintaining the code. Then again, if you followed all these rules religiously, even you wouldn’t be able to maintain the code!
You don’t want to overdo this. Your code should not look hopelessly unmaintainable, just be that way. Otherwise it stands the risk of being rewritten or refactored.
A few excerpts…
Be polite, Never Assert
Avoid the assert() mechanism, because it could turn a three-day debug fest into a ten minute one.
Bedazzling Names
Choose variable names with irrelevant emotional connotation. e.g.:
marypoppins = (superman + starship) / god;
This confuses the reader because they have difficulty disassociating the emotional connotations of the words from the logic they’re trying to think about.
Use Continuation to hide variables
Instead of using
#define local_var xy_z
break up “xy_z” onto two lines:
#define local_var xy\
_z // local_var OK
That way a global search for xy_z will come up with nothing for that file. To the C preprocessor, the “” at the end of the line means glue this line to the next one.
