Effects of cold water (must read)

For those who like to drink cold water, this article is applicable to you. It is nice to have a cup of cold drink after a meal. However, the cold water will solidify the oily stuff that you have just consumed. It will slow down the digestion. Once this "sludge" reacts with the acid, it will break down and be absorbed by the intestine faster than the solid food. It will line the intestine. Very soon, this will turn into fats and lead to cancer. It is best to drink hot soup or warm water after a meal.

A serious note about heart attacks - You should know that not every heart attack symptom is going to be the left arm hurting. Be aware of intense pain in the jaw line.

You may never have the first chest pain during the course of a heart attack. Nausea and intense sweating are also common symptoms. 60% of people who have a heart attack while they are asleep do not wake up. Pain in the jaw can wake you from a sound sleep. Let's be careful and be aware. The more we know the better chance we could survive.

A cardiologist says if everyone who reads this message sends it to 10 people, you can be sure that we'll save at least one life. Read this & Send the link to a friend. It could save a life. So, please be a true friend and send this article to all your friends you care about.

Bad temper

There once was a little boy who had a bad temper. His Father gave him a bag of nails and told him that every time he lost his temper, he must hammer a nail into the back of the fence.

The first day the boy had driven 37 nails into the fence. Over the next few weeks, as he learned to control his anger, the number of nails hammered daily gradually dwindled down.

He discovered it was easier to hold his temper than to drive those nails into the fence.

Finally the ! day came when the boy didn't ose his temper at all. He told his father about it and the father suggested that the boy now pull out one nail for each day that he was able to hold his temper.

…………………..The days passed and the young boy was finally able to tell his father that all the nails are gone. The father took his son by the hand and led him to the fence He said, "You have done well, my son, but look at the holes in the fence. The fence will never be the same.

When you say things in anger, they leave a scar just like this one. You can put a knife in a man and draw it out.

It won't matter how many times you say "I'm sorry", the wound is still there. A verbal wound is as bad as a physical one.

Please forgive me if I have ever left a hole.

The Prophet (peace be upon him) said:

"No one has swallowed back anything more excellent in the sight of Allah, Who is Great and Glorious, than anger he restrains, seeking to please Allah, The Most High."

Al-Tirmidhi Hadith 5116 Narrated by Abdullah ibn Umar

Heaven or Hell

A small story about Great place to work.

A holy man was having a conversation with the Lord one day and said,"Lord, I would like to know what Heaven and Hell are like."

The Lord led the holy man to two doors. He opened one of the doors and the holy man looked in. In the middle of the room was a large round table. In the middle of the table was a large pot of stew which smelled delicious and made the holy man's mouth water. The people sitting around the table were thin and sickly. They appeared to be famished. They were holding spoons with very long handles and each found it possible to reach into the pot of stew and take a spoonful, but because the handle was longer than their arms, they could not get the spoons back into their mouths. The holy man shuddered at the sight of their misery and suffering. The Lord said, "You have seen Hell."

They went to the next room and opened the door. It was exactly the same as the first one. There was the large round table with the large pot of stew which made the holy man's mouth water. The people were equipped with the same long-handled spoons, but here the people were well nourished and plump, laughing and talking. The holy man said, "I don't understand". " It is simple said the Lord, "it requires only one skill.

You see, they have learned to feed each other. While the greedy think only of themselves."

Moral:

Its people's attitude that makes our place of work, a hell or heaven to them!! 'Help and Seek Help' this makes all the difference to each individual's life...and makes our lives hell or otherwise.

Toxins

I do not know about you but I don't like cockroaches. We had them in our house and I did not know anything about hiring exterminators so I decided to get rid of them myself. I bought a sprayer and bought some chemicals to kill them. To measure the chemicals I took a measuring spoon and wired it to the outside of the sprayer. I did this to make sure that I didn't make a mistake and use the measuring spoon again in the house. How could I ever clean it well enough to use it again safely for cooking?

Imagine going in your china closet, getting one of your best crystal glasses, and then using it to measure chemicals to kill the bugs around your house. Then let's imagine that you take it in the house and wash it. Would you dare to use it again? Of course not! It would be contaminated with a toxic film invisible to your eye that might poison anyone who used this glass.

Now imagine that your soul and mine are like this glass. It has been so easy for me to fall victim to the attractive but false temptations of our contemporary world. For example, power, money, liquor, sex, and possessing more and more material possessions are alluring. These are played up so seductively on television and in the media. These can become our golden calves, our false idols! Who has time for God or Church? Perhaps unwittingly or even deliberately I have filled up my glass with these toxins that may kill my soul and potentially others whom I know and love. We call these toxins sin. This mix more importantly is toxic to God and poisons our relationship with Him. The worst of these is so strong that it totally poisons our relationship with God.

Imagine that we determine to do better and try to rid ourselves of these toxins. Can you or I wash the glass of our soul clean enough by ourselves? It would be like trying to wash the lethal chemicals out of our glass with household soap.

Let's assume, however, that we turn to Our Creator, and ask Him with a contrite heart to wash our glass. Is there a sin that He cannot forgive? His Mercy is boundless.

How can we avoid refilling the glass to the brim with another toxic brew? This also is very difficult to do by ourselves. No matter how I have tried to do this the devil always seems to find a way to slip a temptation in my life when I am weak. My glass, you see, is terribly weak and fragile.The toxins once again begin to fill my glass.

Imagine that God not only cleans our glass but also puts a protective substance in the glass that makes it difficult for the devil to introduce any more toxins. Is this possible? The answer is yes. We call this protection grace. The Prayers are the greatest source of this protection. The more grace that we have in our glass the stronger that this protection is. We have the blessing and privilege to be able to meet Our Creator, in Prayers. The grace that He brings surpasses all human understanding. May we get in the habit of praying to God....

Be Still.

When the electric power went out recently, I was impressed by how quiet it was. We live with continual background noise. Indoors we have the sounds of air conditioning, washers, dryers, TVs, computers, telephones, fax machines, answer machines, stereos, and kids. Outdoors are edgers, chainsaws, leafblowers, planes, trains, insects, birds, animals, cars and cell phones.

We have all kinds of noise inside our heads, too. Past tapes, what others have said and done, things we have done or told ourselves. And what about the noise our hearts make? They laugh, cry, remember, and talk to us too!

I don't think of myself as somebody who leads a fast-paced life. That is until I notice how long it takes me to relax and unwind. Getting quiet doesn't happen quickly for me. Sometimes I even have to consciously work at it.

It's a noisy world. And we all need a quiet place in the midst of all the noise. A safe place, where we can BE STILL, and hear the Lord. He very much wants to tell us how much He loves us, and how unique and special we are to Him, maybe give us our day's marching orders.

Today, He has a safe place, somewhere we can go and listen to the quiet. Maybe inside our mind and heart, or perhaps to a physical spot.Journey there and see what wonderful surprises he has planned for this brand new day of Today that we've never seen before.

MAKE A DIFFERENCE

Nov 2, 2007

A teacher in New York decided to honor each of her seniors in high school by telling them the difference they each made. She called each student to the front of the class, one at a time. First she told each of them how they had made a difference to her and the class. Then she presented each of them with a blue ribbon imprinted with gold letters which read, "Who I Am Makes a Difference." Afterwards the teacher decided to do a class project to see what kind of impact recognition would have on a community.

She gave each of the students three more ribbons and instructed them to go out and spread this acknowledgment ceremony. Then they were to follow up on the results, see who honored whom and report back to the class in about a week.

One of the boys in the class went to a junior executive in a nearby company and honored him for helping him with his career planning. He gave him a blue ribbon and put it on his shirt. Then he gave him two extra ribbons and said, "We're doing a class project on recognition, and we'd like you to go out, find somebody to honor, give them a blue ribbon, then give them the extra blue ribbon so they can acknowledge a third person to keep this acknowledgment ceremony going. Then please report back to me and tell me what happened.

Later that day the junior executive went in to see his boss, who had been noted, by the way, as being kind of a grouchy fellow. He sat his boss down and he told him that he deeply admired him for being a creative genius. The boss seemed very surprised. The junior executive asked him if he would accept the gift of the blue ribbon and would he give him permission to put it on him. His surprised boss said, "Well, sure." The junior executive took the blue ribbon and placed it right on his boss's jacket above his heart. As he gave him the last extra ribbon, he said, "Would you do me a favor? Would you take this extra ribbon and pass it on by honoring somebody else? The young boy who first gave me the ribbons is doing a project in school and we want to keep this recognition ceremony going and find out how it affects people.

That night the boss came home to his 14-year-old son and sat him down.

He said, "The most incredible thing happened to me today. I was in my office and one of the junior executives came in and told me he admired me and gave me a blue ribbon for being a creative genius. Imagine. He thinks I'm a creative genius. Then he put this blue ribbon that says 'Who I Am Makes A Difference' on my jacket above my heart. He gave me an extra ribbon and asked me to find somebody else to honor. As I was driving home tonight, I started thinking about whom I would honor with this ribbon and I thought about you. I want to honor you. My days are really hectic and when I come home I don't pay a lot of attention to you. Sometimes I scream at you for not getting good enough grades in school and for your bedroom being a mess, but somehow tonight, I just wanted to sit here and, well, just let you know that you do make a difference to me. Besides your mother, you are the most important person in my life. You're a great kid and I love you!"

The startled boy started to sob and sob, and he couldn't stop crying.

His whole body shook. He looked up at his father and said through his tears, "I was planning on committing suicide tomorrow, Dad, because I didn't think you loved me. Now I know you care. This is the happiest day I've known."

The boss went back to work a changed man. He was no longer a grouch but made sure to let all his employees know that they made a difference. The junior executive helped several other young people with career planning and never forgot to let them know that they made a difference it his life...one being the bosses son. And the young boy and his classmates learned a valuable lesson.

Who you are DOES make a difference.

Remember that!

I give you a blue ribbon.

IS GOD REAL?

IS GOD REAL?
Author Unknown
Mar 13 2008

God are you real ??????
The little child whispered,
"God, speak to me"
And a meadowlark sang.
But the child did not hear.
So the child yelled,
"God, speak to me!"
And the thunder rolled across the sky
But the child did not listen.
The child looked around and said,
"God let me see you"
And a star shone brightly
But the child did not notice.
And the child shouted,
"God show me a miracle!"
And a life was born
But the child did not know.
So the child cried out in despair,
"Touch me God, and let me know you are there!"
Whereupon God reached down
And touched the child.
But the child brushed the butterfly away
And walked away unknowingly

A LITTLE INSPIRATION

A LITTLE INSPIRATION
Author Unknown
Mar 10 2008

When I was quite young, my father had one of the first telephones in our neighborhood. I remember well the polished old case fastened to the wall.
The shiny receiver hung on the side of the box. I was too little to reach the telephone, but used to listen with fascination when my mother used to talk to it.
Then I discovered that somewhere inside the wonderful device lived an amazing person -- her name was "Information Please" and there was nothing she did not know. "Information Please" could supply anybody's number and the correct time.
My first personal experience with this genie-in-the- bottle came one day while my mother was visiting a neighbor. Amusing myself at the tool bench in the basement, I whacked my finger with a hammer.
The pain was terrible, but there didn't seem to be any reason in crying because there was no one home to give sympathy. I walked around the house sucking my throbbing finger, finally arriving at the stairway.
The telephone!
Quickly, I ran for the footstool in the parlor and dragged it to the landing. Climbing up, I unhooked the receiver in the parlor and held it to my ear. "Information Please," I said into the mouthpiece just above my head. A click or two and a small clear voice spoke into my ear.
"Information. " "I hurt my finger. . ." I wailed into the phone. The tears came readily enough now that I had an audience. "Isn't your mother home?"
came the question. "Nobody's home but me." I blubbered "Are you bleeding?"
"No," I replied. "I hit my finger with the hammer and it hurts." "Can you open your icebox?" she asked. I said I could. "Then chip off a little piece of ice and hold it to your finger," said the voice.
After that, I called "Information Please" for everything. I asked her for help with my geography and she told me where Philadelphia was. She helped me with my math. She told me my pet chipmunk that I had caught in the park just the day before would eat fruits and nuts. Then, there was the time Petty, our pet canary died. I called "Information Please" and told her the sad story. She listened, then said the usual things grown-ups say to soothe a child. But I was UN-consoled. I asked her, "Why is it that birds should sing so beautifully and bring joy to all families, only to end up as a heap of feathers on the bottom of a cage?"
She must have sensed my deep concern, for she said quietly, "Paul, always remember that there are other worlds to sing in." Somehow I felt better.
Another day I was on the telephone. "Information Please."
"Information, " said the now familiar voice.
"How do you spell fix?" I asked.
All this took place in a small town in the Pacific northwest. When I was 9 years old, we moved across the country to Boston. I missed my friend very much. "Information Please" belonged in that old wooden box back home, and somehow never thought of trying the tall, shiny new phone that sat on the table in the hall.
As I grew into my teens, the memories of those childhood conversations ever really left me. Often, in moments of doubt and perplexity I would recall the serene sense of security I had then. I appreciated now how patient, understanding, and kind she was to have spent her time on a little boy.
A few years later, on my way west to college, my plane put down in Seattle.
I had about half an hour or so between planes. I spent 15 minutes or so on the phone with my sister, who lived there now. Then without thinking what I as doing, I dialed my hometown operator and said, "Information, Please."
Miraculously, I heard the small, clear voice I knew so well, Information. "
I hadn't planned this but I heard myself saying, "Could you please tell me how to spell fix?"
There was a long pause. Then came the soft spoken answer, "I guess your finger must have healed by now."
I laughed. "So it's really still you,' I said. "I wonder if you have any idea how much you meant to me during that time."
"I wonder," she said, "if you know how much your calls meant to me."
"I
never had any children, and I used to look forward to your calls."
I told her how often I had thought of her over the years and I asked if I could call her again when I came back to visit my sister.
"Please do, she said. "Just ask for Sally."
Three months later I was back in Seattle. A different voice answered "Information. " I asked for Sally.
"Are you a friend?" She said.
"Yes, a very old friend," I answered.
"I'm sorry to have to tell you this, she said. Sally had been working part-time the last few years because she was sick. She died five weeks ago." Before I could hang up she said, "Wait a minute. Did you say your name was Paul?"
"Yes."
"Well, Sally left a message for you. She wrote it down in case you called.
Let me read it to you." The note said, "Tell him I still say there are other worlds to sing in. He'll know what I mean."
I thanked her and hung up. I knew what Sally meant.
Never underestimate the impression you may make on others.

Internal Coding Guidelines

Table of Contents

1. Introduction 1

2. Style Guidelines 2

2.1 Tabs &
Indenting 2

2.2 Bracing 2

2.3 Commenting 2

2.3.1 Documentation Comments... 2

2.3.2 Comment Style............ 3

2.4 Spacing 3

2.5 Naming 4

2.6 Naming
Conventions 4

2.6.1 Interop Classes........ 4

2.7 File
Organization 5

1. Introduction

First, read the .NET Framework Design
Guidelines. Almost all naming conventions, casing rules, etc., are spelled out
in this document. Unlike the Design Guidelines document, you should treat this
document as a set of suggested guidelines. These generally do not effect the customer
view so they are not required.

2. Style Guidelines

2.1 Tabs & Indenting

Tab characters (\0x09) should not be used
in code. All indentation should be done with 4 space characters.

2.2 Bracing

Open braces should always be at the
beginning of the line after the statement that begins the block. Contents of
the brace should be indented by 4 spaces. For example:

if (someExpression)

{

DoSomething();

}

else

{

DoSomethingElse();

}

“case” statements should be indented from
the switch statement like this:

switch
(someExpression)

{

case 0:

DoSomething();

break;

case 1:

DoSomethingElse();

break;

case 2:

{

int n = 1;

DoAnotherThing(n);

}

break;

}

Braces should never be considered
optional. Even for single statement blocks, you should always use braces. This
increases code readability and maintainability.

for (int i=0;
i<100; i++) { DoSomething(i); }

2.3 Single line statements

Single line statements can have braces
that begin and end on the same line.

public class Foo

{

int bar;

public int Bar

{

get { return bar; }

set { bar = value; }

}

}

It is suggested
that all control structures (if, while, for, etc.) use braces, but it is not
required.

2.4 Commenting

Comments should be used to describe
intention, algorithmic overview, and/or logical flow. It would be ideal, if from reading the comments alone, someone
other than the author could understand a function’s intended behavior and
general operation. While there are no minimum comment requirements and
certainly some very small routines need no commenting at all, it is hoped that
most routines will have comments reflecting the programmer’s intent and
approach.

2.4.1 Copyright notice

Each file should start with a copyright
notice. To avoid errors in doc comment builds, you don’t want to use
triple-slash doc comments, but using XML makes the comments easy to replace in
the future. Final text will vary by product (you should contact legal for the
exact text), but should be similar to:

//-----------------------------------------------------------------------

// <copyright file="ContainerControl.cs"
company="Microsoft">

// Copyright (c) Microsoft
Corporation. All rights reserved.

// </copyright>

//-----------------------------------------------------------------------

2.4.2 Documentation Comments

All methods should use XML doc comments.
For internal dev comments, the <devdoc> tag should be used.

public class Foo

{

/// <summary>Public stuff about the method</summary>

/// <param name=”bar”>What a neat parameter!</param>

/// <devdoc>Cool internal stuff!</devdoc>

///

public void MyMethod(int bar) { … }

}

However, it is common that you would want
to move the XML documentation to an external file – for that, use the
<include> tag.

public class Foo

{

/// <include file='doc\Foo.uex'
path='docs/doc[@for="Foo.MyMethod"]/*' />

///

public void MyMethod(int bar)
{ … }

}

UNDONE§ there is a big doc with all the
comment tags we should be using… where is that?

2.4.3 Comment Style

The // (two slashes)
style of comment tags should be used in most situations. Where ever possible, place comments above the code
instead of beside it. Here are some examples:

// This is required for WebClient to work through the proxy

GlobalProxySelection.Select = new
WebProxy("http://itgproxy");

// Create object to access Internet resources

//

WebClient myClient = new WebClient();

Comments can be placed at the end of a
line when space allows:

public class SomethingUseful

{

private
int itemHash; // instance member

private
static bool hasDoneSomething; // static member

}

2.5 Spacing

Spaces improve readability by decreasing
code density. Here are some guidelines for the use of space characters within
code:

• Do use a single space after a comma between function arguments.
  
  Right: Console.In.Read(myChar, 0, 1);
  
  Wrong: Console.In.Read(myChar,0,1);


• Do not use a space after the parenthesis and
  function arguments
  
  Right: CreateFoo(myChar, 0, 1)
  
  Wrong: CreateFoo( myChar, 0, 1 )


• Do not use spaces between a function name and
  parenthesis.
  
  Right: CreateFoo()
  
  Wrong: CreateFoo ()


• Do not use spaces inside brackets.
  
  Right: x = dataArray[index];
  
  Wrong: x = dataArray[ index ];


• Do use a single space before flow control statements
  
  Right: while (x == y)
  
  Wrong: while(x==y)


• Do use a single space before and after comparison operators
  
  Right: if (x == y)
  
  Wrong: if (x==y)

2.6 Naming

Follow all .NET Framework Design
Guidelines for both internal and external members. Highlights of these include:

• Do not use Hungarian notation


• Do not use a prefix for member variables
  (_, m_, s_, etc.). If you want to distinguish between local and member
  variables you should use “this.” in C# and “Me.”
  in VB.NET.


• Do use camelCasing for member variables
  


• Do use camelCasing for parameters


• Do use camelCasing for local variables


• Do use PascalCasing for function,
  property, event, and class names


• Do prefix interfaces names with “I”


• Do not prefix enums, classes, or delegates
  with any letter

The reasons to extend the public rules (no
Hungarian, no prefix for member variables, etc.) is to produce a consistent
source code appearance. In addition a goal is to have clean readable source.
Code legibility should be a primary goal.

2.7 Naming Conventions

2.7.1 Interop Classes

Classes that are there for interop
wrappers (DllImport statements) should follow the naming convention below:

• NativeMethods – No suppress unmanaged code
  attribute, these are methods that can be used anywhere because a stack
  walk will be performed.


• UnsafeNativeMethods – Has suppress unmanaged code
  attribute. These methods are potentially dangerous and any caller of these methods must do a
  full security review to ensure that the usage is safe and protected as no
  stack walk will be performed.


• SafeNativeMethods – Has suppress unmanaged code
  attribute. These methods are safe and can be used fairly safely and the
  caller isn’t needed to do full security reviews even though no stack walk
  will be performed.

class NativeMethods

{

private NativeMethods() {}

[DllImport(“user32”)]

internal static extern void
FormatHardDrive(string driveName);

}

[SuppressUnmanagedCode]

class UnsafeNativeMethods

{

private UnsafeNativeMethods()
{}

[DllImport(“user32”)]

internal static extern void
CreateFile(string fileName);

}

[SuppressUnmanagedCode]

class SafeNativeMethods

{

private SafeNativeMethods() {}

[DllImport(“user32”)]

internal static extern void
MessageBox(string text);

}

All interop classes must be private, and all methods must be internal. In addition a private constructor should be provided to
prevent instantiation.

2.8 File Organization

• Source files should contain only one public
  type, although multiple internal classes are allowed


• Source files should be given the name of the
  public class in the file


• Directory names should follow the namespace
  for the class

For example, I would expect to find the
public class “System.Windows.Forms.Control” in
“System\Windows\Forms\Control.cs”…

• Classes member should be alphabetized, and grouped into sections (Fields, Constructors,
  Properties, Events, Methods, Private interface implementations, Nested
  types)


• Using statements should be inside the
  namespace declaration.

namespace MyNamespace

{

using System;

public class MyClass : IFoo

{

//
fields

int foo;

//
constructors

public MyClass() { … }

//
properties

public int Foo { get { … } set { … } }

//
events

public event EventHandler FooChanged { add { … } remove {
… } }

//
methods

void DoSomething() { … }

void FindSomethind() { … }

//private interface implementations

void IFoo.DoSomething() {
DoSomething(); }

// nested types

class NestedType { … }

}

}

Get Rid of These Bad Work Habits

By Anthony Balderrama, CareerBuilder.com writer

Who doesn’t have at least one habit that drives everyone else insane? You might bite your nails, slurp your coffee or tap your pen incessantly. Annoying? Yes. Serious problems? Not really.

In the office, however, some habits can go beyond annoying your co-workers; they can damage your career.

For the sake of your career and your co-workers’ sanity, here’s a list of bad work habits that can harm your career and how you can break them. If you’re guilty of one (or more), it’s time to get them under control.

Bad Habit: Missing deadlines.
What you think: “If it’s only a little late, it doesn’t mean anything.”
What it really says: Your colleagues and boss can’t count on you.
What to do: Don’t view deadlines as negotiable. Remind yourself that people are counting on you to do your job well, which includes completing tasks on time. Even if you just barely missed the deadline and everything turned out OK, you probably caused your teammates a lot of anxiety and extra work, which they won’t forget.

Bad Habit: Dressing unprofessionally.
What you think: “I’m the office free spirit with a quirky sense of style!”
What it really says: You don’t take the job seriously.
What to do: You don’t have to be a boring dresser to be professional, but you shouldn’t look like you’re about to go clubbing or strutting down a runway. Take a cue from your co-workers to see what’s considered acceptable in the office.

Bad Habit: Not being punctual.
What you think: “As long as I get all my work in, nobody cares.”
What it really says: You think your time is more important than everybody else’s.
What to do: Stick to the schedule. Everyone in your office would like to sleep in a little or leave early, but they don’t because people rely on them to be on time.

Bad Habit: Checking your e-mail, playing games, shopping.
What you think: “I’m discreet.”
What it really says: You’re not doing your job.
What to do: Keep the fun stuff to a minimum. Most employers don’t mind if you check your e-mail every once in awhile or read your favorite blog for a few minutes in the morning. They begin to care when you minimize that game of Scrabulous every time they walk by your desk. You’re being paid to work, not play.

Bad Habit: Gossiping.
What you think: “I’m just saying what I heard.”
What it really says: You can’t be trusted.
What to do: Sure, everybody gossips a little here and there, but it shouldn’t be your livelihood. Eventually you’ll gain a reputation for not keeping anything confidential –whether it’s a personal matter or work-related. Plus, your chattering could end up hurting somebody’s feelings or reputation.

Bad Habit: Being negative.
What you think: “Everybody complains.”
What it really says: You’re the person to avoid.
What to do: It’s natural to grumble about work once in awhile. If you gripe and moan when you’re asked to do anything, however, people will not only get annoyed, they’ll wonder why you don’t just quit. Keep in mind that work isn’t always fun; keep the complaints to a minimum.

Bad Habit: Trying to be everybody’s best friend.
What you think: “I’m just sociable.”
What it really says: You don’t know how to set boundaries.
What to do: It’s not uncommon for friendships to develop at work, but don’t expect it to happen with everybody. Unless you have reason to do otherwise, treat your superiors, colleagues and subordinates like professionals, not like drinking buddies.

Bad Habit: Burning bridges.
What you think: “I’ll never see them again.”
What it really says: You’re not a professional who thinks about the future.
What to do: As much as you dream of telling off your boss or co-workers after you’ve handed in your resignation, restrain yourself. People change jobs, companies merge – someone you dissed in the past may end up being your boss down the road.

Bad Habit: Always being the funny one.
What you think: “People love me.”
What it really says: You’re really annoying.
What to do: There’s nothing wrong with being funny – most people do like a good sense of humor. Just remember that not everybody wants to hear your sarcastic quips and “Godfather” impersonations every five minutes.

Bad Habit: Forgetting you have neighbors.
What you think: “I’m not as annoying as they are.”
What it really says: You’re inconsiderate.
What to do: Do unto your co-workers as you’d want them to do unto you. Your hour-long conference call on speakerphone is just as irksome to your cube mates as theirs are to you.

Anthony Balderrama is a writer and blogger for CareerBuilder.com. He researches and writes about job search strategy, career management, hiring trends and workplace issues.