Thread regarding Honeywell International Inc. layoffs

So true and I didnt think anyone hated America as much as obummer.

India is the reason I left Honeywell. Well, that and Mexico.

Dave's two favorite countries.

He hates America so much he could be Obama.

I wondered what happened to their quality. The garbage they produce now is nothing more than a plug in turd.

OK, regarding your comment...

"Be professional and human decency when posting stuffs. Chinese, Indian, red, yellow, or blue do not create the problem. Some abused WFH policy. 8 hrs day is an answer"

First, by your grammar, it's obvious you're a little biased to my assertions.

Second, "red, yellow, or blue"? LOL! I told you, race has nothing to do with it! It's culture you moron. I would rather deal with a hard-working Japanese guy (I believe that YOU would call him 'yellow') than a white guy from Albania. Race is meaningless, but culture matters.

Be professional and human decency when posting stuffs. Chinese, Indian, red, yellow, or blue do not create the problem. Some abused WFH policy. 8 hrs day is an answer

I agree with all of these comments, and before anybody tries to pull the race card, don't. There's nothing racist about the criticisms here. It's all about culturally accepted levels of expected quality. I've seen this in many developing countries. There is a 'good enough' mentality that just doesn't cut it with the vast majority of our customers, which are mostly based in North America and Europe (at least in my SBU). Just take a look at any piece of source code for a product that moved to India or China from North America or Europe. If you can actually get them to agree to share it with you, you'll immediately be able to see which software team wrote what. It's embarrassing.

Yep! I've got loads of inside knowledge on how my program runs and how to fix issues. If davy and timmy think for one second that I'm sharing that information with any offshore person, they are sorely mistaken. They can fire me if they want to but I still win; that knowledge is staying right in my brain. Go ahead and try to figure out how this thing works without me, it'll take them years and I will have already found a better job with a competing company. So in the end, davey, timmy, dairyass, all three of you can svck my @$$ and my b@lls!

Agree with the Mexicali comment. I guess that's why ALT continues to put Torr. Work down there.

Add Mexicali to the list of employees that cant find their a$$ with both hands.

poster HON layoff survival guide: I worked with guys when Xerox was doing the low cost region thing. You are absolutely correct. Everyone read and memorize this.

HON layoff survival guide:

Learn from us ninja-experts that have already gone through what HON is putting you guys through as it gradually replaces each of you domestic counterparts with very cheap offshore workers.

Don't write any code comments, or if you do, don't explain how things work – this should be easy

Create silos of local work groups and work face to face… Provide no email on how/what you've done.

If overseas teams ask you how to do things, give a quick and broad brush overview, no details are to be provided.

Write more complicated code that is difficult to understand, provided it does not affect the underlying performance/reliability.

Don't write complete design documents. IF you write design documents, write enough to get management to think it's done, but not enough for engineers offshore to do anything useful with it.

Occasionally, take a vacation day off on short notice, and let things just "blow up" after you hand off your work to offshore teams. When you come back and things are completely not working, send lots of email about what a terrible job people have done...

Always blame problems on offshore teams, no matter how small. 8. Always blame the reason why you problems can't be fixed earlier is because there is a 15+hour timezone difference between headquarters and those remote offices.

Hold meetings at times that is convenient for you but in the middle of the night for those offshore teams.

Make sure your meetings you conduct locally are as efficient as possible and make your local U.S. totally in sync and ahead of the work schedule before you even meet with the offshore team. That way, it makes them look incompetent.

The best meetings are the ones held at 5:00pm PST on Friday, since that will be Saturday overseas, so the ones that most won't show up.And the ones that do show up, end up having to take time off their personal schedule to do it...Make sure this is a reoccurring weekly meeting...

At the last minute, reschedule those meetings for the next week (but continue to meet locally and carry on your business).

Make sure you send out a meeting notes to senior management, indicating who attended and more importantly, who didn't attend...

When someone screws up overseas, always make sure you take the initiative to fix the problem, and make sure you send out 5+ emails telling management how you fixed the problem, describing in extreme detail how things got so screwed up and how you fixed it. And most importantly, if you're going down, you might as well create as much havoc internally inside the company as possible. Nothing is worse more than a company has so much internal conflict that efficiency and productivity comes to a halt..It's 10x worse than any sort of external competition....

And that's the predicament corporations and will put the company in when it starts trying to just save on "cost" by offshoring....

Anyhow, I claim no ownership of this thread as it was completely taken from our good friends at Xerox @H8MXdSj