Monday, March 15, 2010

50 Worst of the Worst (and Most Common) Job Interview Mistakes

You may have heard the horror stories--job hunters who take phone calls or text during an interview, or bring out a sandwich and start chomping, or brush their hair, or worse. You wouldn't do any of those things, would you? Of course not.

But there are tons of other job interview no-no's you may not have thought of. Or that you've forgotten. The job hunting trail is long and arduous, and a little refresher course can't hurt. So for your edification and enjoyment, here are 50 of the worst and most common job interview mistakes:

1. Arriving late.
2. Arriving too early.
3. Lighting up a cigarette, or smelling like a cigarette.
4. Bad-mouthing your last boss.
5. Lying about your skills/experience/knowledge.
6. Wearing the wrong (for this workplace!) clothes.
7. Forgetting the name of the person you're interviewing with.
8. Wearing a ton of perfume or aftershave.
9. Wearing sunglasses.
10. Wearing a Bluetooth earpiece.
11. Failing to research the employer in advance.
12. Failing to demonstrate enthusiasm.
13. Inquiring about benefits too soon.
14. Talking about salary requirements too soon.
15. Being unable to explain how your strengths and abilities apply to the job in question.
16. Failing to make a strong case for why you are the best person for this job.
17. Forgetting to bring a copy of your resume and/or portfolio.
18. Failing to remember what you wrote on your own resume.
19. Asking too many questions.
20. Asking no questions at all.
21. Being unprepared to answer the standard questions.
22. Failing to listen carefully to what the interviewer is saying.
23. Talking more than half the time.
24. Interrupting your interviewer.
25. Neglecting to match the communication style of your interviewer.
26. Yawning.
27. Slouching.
28. Bringing along a friend, or your mother.
29. Chewing gum, tobacco, your pen, your hair.
30. Laughing, giggling, whistling, humming, lip-smacking.
31. Saying "you know," "like," "I guess," and "um."
32. Name-dropping or bragging or sounding like a know-it-all.
33. Asking to use the bathroom.
34. Being falsely or exaggeratedly modest.
35. Shaking hands too weakly, or too firmly.
36. Failing to make eye contact (or making continuous eye contact).
37. Taking a seat before your interviewer does.
38. Becoming angry or defensive.
39. Complaining that you were kept waiting.
40. Complaining about anything!
41. Speaking rudely to the receptionist.
42. Letting your nervousness show.
43. Overexplaining why you lost your last job.
44. Being too familiar and jokey.
45. Sounding desperate.
46. Checking the time.
47. Oversharing.
48. Sounding rehearsed.
49. Leaving your cell phone on.
50. Failing to ask for the job.

Monday, February 22, 2010

Redirecting an HTTP Request to HTTPS

Navigating between the public and restricted areas of your site (that is, between HTTP and HTTPS pages) is an issue because a redirect always uses the protocol (HTTPS or HTTP) of the current page, not the target page.

After a user logs on and browses pages in a directory that is secured with SSL, relative links such as "..\publicpage.aspx" or redirects to HTTP pages result in the pages being served using the HTTPS protocol, which incurs an unnecessary performance overhead. To avoid this, use absolute links such as "http://servername/appname/publicpage.aspx" when redirecting from an HTTPS page to an HTTP page.

Similarly, when you redirect to a secure page (for example, the logon page) from a public area of your site, you must use an absolute HTTPS path, such as "https://servername/appname/secure/login.aspx" instead of a relative path, such as "restricted/login.aspx." For example, if your Web page provides a logon button, use the following code to redirect to the secure login page.

Copy Code
private void btnLogon_Click( object sender, System.EventArgs e )
{
// Form an absolute path using the server name and v-dir name
string serverName =
HttpUtility.UrlEncode(Request.ServerVariables["SERVER_NAME"]);
string vdirName = Request.ApplicationPath;
Response.Redirect("https://" + serverName + vdirName +
"/Restricted/Login.aspx");

}

Sunday, February 21, 2010

Usb flash drive icon changes into folder icon

This issue may have resulted from a virus infection on the machine the drive was plugged into.

You’ll need to delete the file autoruns.inf located on your flash drive.

By default, Windows hides this file, so before you can delete it you must make a couple of changes (you may reverse these after you’ve finished):

Open My Computer
Tools
Folder Options…
Click on the View tab
Under “Hidden files and folder” choose “Show hidden files and folders”
Remove the tick from “Hide protected operating system files (Recommended)
OK

Go back to My Computer and click on your flash drive. If you can’t open it that way, try right clicking on it and choose “Explore.”

Find the autoruns.inf file, right click on it and choose “Delete.” Confirm “Yes.”

Unplug and re-plug the drive in. You should be back to normal.


Hope that helps.