Top 10 operating system stinkers

1. OS/360, 1964
2. ITS (Incompatible Timesharing System), late 1960s
3. GNU Hurd, launched in 1983, still incomplete
4. Windows 1.01, 1985
5. MS-DOS 4.0, 1988
6. SCO Open Desktop, 1989
7. JavaOS, 1996
8. Windows Me (Millennium Edition), 2000
9. Lindows/Linux XP Desktop, 2001/2006
10. Windows Vista, 2006

what do the ultimate gift consists?

The gift that diverts the life along the unique & valuable path is ultimate.
these unltimate gift are :

Gift 1: The gift of work - If u got the chance to work,take this work as gift.

Gift 2: The gift of money - This gift is too worthfull.

Gift 3: The gift of friends -Friends is the most essential gift given by the existing god.

Gift 4: The gift of learning - Use yur time to learn,because leaning is the most valuable gift.

Gift 5: The gift of problems - Problems are gifts,accept it.

Gift 6: The gift of family - The first gift,but some are deprive of it.

Gift 7: The gift of laughter - It's a gift.plz open it,which keeps healthy & gives power to life.

Gift 8: The gift of dreams - This gift can do anything.it can change the whole world.so dream & see the effects.

Gift 9: The gift of giving - You think sometimes this gift can ruined you.but believe it 'll not do so.

Gift 10: The gift of gratitude - Its a gift you should have it in plenty of ammount.

Gift 11: The gift of the day - A lovely gift.spent this gift with full of love & happiness.

Gift 12: the gift of love - The final gift,everyone borns for.have it,its yours.

check out have you ever lost any of the above gift in the life.if lost,try to grab it.

7 mistakes to avoid when applying for tech job

In this economy, even having the experience may not be enough

Greg Schaffer

(Computerworld) My eyes are blurry from reviewing over 40 résumés for a network administrator position, and for good reason. More than half of the résumés did not make it past my initial review. While I had to reject some candidates because of lack of experience (or, rather, lack of clearly demonstrated required experience), others had errors in their application packages that lowered their ranking -- errors that could have been easily corrected.(And yes, I literally do rank résumés, based on years and type of experience but also on other nontechnical variables such as communications ability.)

Of course, the traditional job-seeking advice still applies. Always follow résumé best practices -- proper spelling, good organization, consistent font and so on. Realize, too, that if you simply do not meet the required minimum experience, it's very unlikely that you will win the job. Beyond that, if you avoid these all-too-common mistakes that I have seen over years of filling network administrator positions, you'll boost your chance of landing the job.

Mistake 1:your objective is unclear

When I review résumés for a network administrator position, if the applicant chooses to include a section about his objectives, I hope to see something related to networking. Likewise, managers filling spots for security, databases, Web development and other specialties are looking for specifics that show a candidate is a good fit for the job. However, I often see nonsensical statements such as, "I'm seeking an interesting and challenging career position." This conveys very little.

Instead, something directly related to the position you're seeking would be appropriate. Suppose, for example, that you applied for a network administrator job at a community college. "Utilizing my experience to expand and maintain the network to enhance the pedagogical mission of the college" says that you see this as a challenge and that you understand the business of the place you are applying to.

This leads to two subpoints. First, whenever possible, show you understand how technology affects the business. Second, decide if an objective section is really necessary. Some people opt to substitute a short description of their professional offerings, which, if done well, can effectively convey both your goals and understanding of the business as well as serve as a snapshot of your most desirable skills.

Mistake 2:you've listed old skills

I'd like to say it has been some time since I've received a résumé that listed in a skills section "Windows 3.11 for Workgroups," but unfortunately it hasn't. At least it's been a while since I've seen DOS 3.2 referenced.

I'm not trying to downplay achievements from over 10 years ago. Yes, I also remember loading Trumpet Winsock before Microsoft Corp. incorporated TCP/IP into Windows, and back in the day, I was a Novell 3.12 CNE. But how relevant are those skills today? They're really not, and including them in a résumé gives the impression of trying to fill the application with fluff.

If you do want to mention that you were proficient in tapping ThickNet, leave it for the job description section. When I look at a skills section, I am trying to directly correlate the candidate's skills with what I need. Of course, some network skills that don't change much over time can be listed. If, for example, the ad calls for Dynamic Host Configuration Protocol administration experience and you managed DHCP 10 years ago, by all means put it in the skills section. It's the technology no longer in use that should be left behind.

Mistake 3:You've created an 'alphabet soup' explosion

What is one thing that unites all aspects of information technology? Acronyms. Sometimes I think there is a secret subcommittee of the IETF that follows some obscure RFC for creating network acronyms. It follows that network administrators are often guilty of AERs (acronym-enhanced résumés).

Like listing older skills, a seemingly endless stream of acronyms is like data padding in an ICMP packet; it adds only space. If you indicate experience configuring enterprise core LAN routers, I would expect that you understand TCP/IP, SNMP, TFTP, VLSM, VLAN, possibly NTP and VPN, and at least one routing protocol such as OSPF or RIP. There is no need to list them.

That's not to say that acronyms and protocols should not be mentioned at all. But if you do, be prepared to back it up. My favorite interview question is to have applicants describe the differences between TCP and UDP, and if you've put TCP/IP anywhere on the résumé, you'd better get the answer right. Actually, that's one of those questions a netadmin candidate should be able to answer correctly no matter what.

Mistake 4:You misuse industry jargon

One of my biggest pet peeves when reviewing candidates' documents is when I come across a term or statement that has the unintended effect of conveying lack of experience. It may be technically correct but is only seen in textbooks and study materials and not used in the real world.

My favorite example of this is "worked on networks with a star topology." I don't recall ever asking a vendor what star-topology products they offer. I know, and so do they, that a switch is a device that distributes connectivity physically and logically from a single location. Including such phrases tells me that you do not have actual, significant experience working on enterprise networks.

In addition, don't use buzzwords if you don't know what they mean. If you say you work with both single-mode and multimode fiber, you'd better be prepared to explain the differences and the uses of each.

Mistake 5:You're unclear what 'network administrator' means

Some IT professionals have a narrow definition of what a network administrator does: works on Layer 2 and up enterprise transport equipment -- in other words, switches and routers. Also included may be such ancillary duties such as DNS and DHCP administration or firewall configuration and support.

Others, however, define "network administrator" to include server and systems administration. This would include one who primarily works on the end points of a client/server network. In these cases, administration of the network may not be as important, perhaps because the company has a simple network.

Whatever the position, the point is to look beyond the title of the job you're interested in and really examine what the employer is looking for. In my case, I had several applicants who had significant experience configuring, administering to and maintaining Windows servers but zero experience configuring switches and routers even though positions they held had "network" in the job title. They were rejected because I needed a router jockey.

Mistake 6:You're vague about your experience, or you're just downright confusing

Statements such as "works closely with the network team," "assisted in network installation" or "supported networks" convey nothing about relevant network experience. I work closely with my tax adviser; does that make me an accountant? You need to clarify relevant experience.

Also, if applying for an enterprise position, be sure you meet the experience required. If a position requires experience with administering enterprise routers, don't assume that setting up linksys routers qualifies. All that does is convey that you do not understand the difference between SOHO and enterprise networking.

Finally, and this may seem obvious, match the experience to each position, even if it means some repetition. Otherwise, it is difficult to determine the years of experience of, say, configuring routers. I reviewed one résumé in which the candidate described all of her skills first, then simply listed her position titles and dates of employment afterward. Since it was not possible to match duty with position, I could not the calculate number of years experience per duty. The résumé ended up in the reject stack because I was unable to accurately determine if the candidate met the minimum experience requirements.

Mistake 7:You lose sight of the goal

Remember, your résumé should be directed to a technology professional. Yes, human resources may review the application as well, but ultimately the position's supervisor (and most probably peers) will choose who to interview. Your résumé should talk to them.

Do not forget your goal. Get your foot in the door for a face-to-face interview. Craft an application strategy to do so. If you're applying to be a network administrator, have a fellow network administrator or two review your application, and ask them their impressions from a peer perspective. Does it convey that you know networking? If the answer is "yes," you're well on the way to landing that job.

Top 10 Careers with highest job satisfaction

iTop10 has just published findings of a survey to analyze which are the careers that give highest job satisfaction. It is indeed very much essential that one achieves job satisfaction in one’s job, whatever it may be, to make one’s life delightful. There are hundreds of hottest job openings out there, but that may not essentially be satisfying for you… In today’s world most of the people, despite enjoying prestigious positions in various top-class organizations, are not fully satisfied with it. The reasons may vary from one individual to another. But the most important question is: ”What career will end this quest for satisfaction / happiness?”

Hottest Job openings also conducted a similar research backend and came out with a strange outcome that Software-related jobs, though are among highly satisfying jobs, still lag behind careers like singing, writing, painting, etc. when it comes to job satisfaction. With due respect to iTop10, here is my own list of the careers considered as the most satisfying:

1. Singers & Actors — the most relaxed creatures… Even if their movies / songs are not so popular with people, they still rake in loads of money! Includes cheerleaders too!!
2. Authors — Most of the people don’t understand what they write, and hence this community is absolutely safe from being dodged from their jobs…
3. Fire fighters — Awesome! Hats off to these guys who make life safe, colourful, delightful & worth living.
4. Doctors — great contribution to keeping people healthy.
5. Professors — Hmmm. Highly satisfying as long as pupils listen to them!
6. Painters and sculptors — Ditto authors. Only they understand what they have created, therefore no competition and hence highly satisfied…
7. Software-related
   The most fascinating and amazing of all fields… Not any more. People associated with developing software or any related fields are found to be highly satisfied. A possible reason may be the highly addictiveness of this profession. I have taken efforts to further drill down this stream and have listed the software roles based on their satisfaction levels:
   • Chief Technology Officer (CTO)
   • Chief Program Manager
   • Project Manager
   • Business Analyst
   • Software Tester
   • Knowledge Manager
   • Onshore/Offshore Coordinator
   • Team Lead
   • Software Developer — the most dreaded community!
8. Criminal investigators — making life hell for those on the wrong side of law. Definitely interesting if they themselves are not involved!!!
9. Career counselors — Teaching (read, Preaching) is always a pleasure. They may not be sure of where their own career would go, but they would certainly guide others to choose the right path…
10. Education administrators — I don’t know if they really do anything!!! :)

Knowing where to tap makes all the difference

A giant ship was making its way in the Pacific when its engine failed. The ship’s owners tried one expert after another, but none of them could figure out how to fix the engine.

Then they brought in an old man who had been fixing ships since he was a young boy. He carried a large bag of tools with him, and when he arrived, he immediately set to work. He inspected the engine very carefully, top to bottom.

Two of the ship’s owners were there, watching this man, hoping he would know what to do. After looking things over, the old man reached into his bag and pulled out a small hammer and gently tapped something. Instantly, the engine lurched into life.

He carefully put his hammer away. The engine was fixed!

A week later, the owners received a bill from the old man for ten thousand dollars.

“What?” the owners exclaimed. “He hardly did anything!”

So they wrote the old man a note saying, “Please send us an itemized bill.”

The man sent a bill that read:

Tapping with a hammer …………………. $ 2.00
Knowing where to tap…………………….. $ 9998.00

Effort is important, but knowing where, can make all the difference.

Perspective

“You don’t get paid for the hour. You get paid for the value you bring to the hour.”
- Jim Rohn

“Where to Tap“, brings to our attention a critical component in an otherwise well accepted philosophy, rather crisply. It tells us that, “where” we put efforts to achieve our objectives, is as important or perhaps a shade more important than “what”. So, we must never overlook this aspect in our endeavour to pursue our goals coz it might just make all the difference.

As Elbert Hubbard said, “Folks who never do any more than they get paid for, never get paid for any more than they do.”

We also need to make a visible impact by our efforts and make our point such that there is no room for debate about why we deserve the acknowledgement we claim. Otherwise, we may end up with only $ 2 instead of the $ 10,000, for our efforts!!

Tata to sponsor Team Ferrari in next Formula 1 race

Times Now just reported that India’s most renowned corporate brand, Tata and one of the biggest teams in Formula 1, Team Ferrari has inked a deal wherein the Tata’s will sponsor Team Ferrari in the forthcoming race. It may be recollected that in last 3 years, India participated in the Formula 1 racing with Narayan Karthikeyan making a mark. Now this year, India has gone ahead with sponsoring entire racing team!

Ratan Tata was quite happy with this global branding deal, under which fans will see the Ferrari drivers flaunting an Indian brand. Another first for India, A really good news for Tata’s and for India too, especially after the recent terrorist attacks that thrown Mumbai out of gear.

Hats off to Ratan Tata for inking this fantastic deal. I am feeling proud to be an Indian!

No more missed tickets to your favorite concert

I am a great fan of Bon Jovi. I almost die for his songs like It’s my Life. I always wanted to attend one of his concerts, but getting tickets was next to impossible. Especially when I hardly had any time to stand in queues or to run around after agents. I was also on similar sticky wicket when Britney Spears came to my town for a live event, and I promised myslef that this time I will not leave any stone unturned to attend my love’s event. (Yes, I love Britney!) Just around this time, one of my friend suggested Seatwave - the Fan-to-Fan online ticket exchange community. It’s an online marketplace where fans can trade tickets for concerts, theatre, sport, special events and just about any other kind of live event.

This concept is actually driven by simple yet powerful processes: TicketIntegrity™ - tickets come only from legitimate sources and no fraudulent practices followed here; and TicketCover™ - All Seatwave tickets (Concert tickets / sports / theatre) are covered for event cancellation ensuring that you get the full cost of your ticket back and not just the face value. So there are no hassles of standing in surpentine queues, rubbing your shoulders (in the wrong way) with other fans / goons, loosing precious time, etc. Seatwave guarantees that you’ll get your tickets well in advance of the actual event, and in case you didn’t get, they will be happy to refund all your money! I am hooked in guys, and you?