I flew right after 911, like the week after, knowing it would be the safest time to go (despite my family having nervous breakdowns). But afterwards, with all the "cost measures" put into place, especially those that bought into the magic math Indian myths, I stopped having faith in any programs that relied on transferring engineering or development to lower cost countries. This included ALL aerospace (remember all the air traffic control and ticket system failures?) and a lot of precision manufacturing. The facilities people and janitorial staff did not deserve the horrors perpetrated upon them. Haven't taken a plane in over a decade, would have been longer but family needs prevailed that time.
Boeing was under great pressure to produce a competitor for the Airbus A220 but the only airframe they had that could do that was the 737, they had to do this quickly to have any sort of chance to compete.
They cut corners in planning, tooling, tech authoring and configuration, these were savage cuts which the senior maintainers and engineers warned would lead to accidents. On top of this they wont woke as this post shows, Don't fly in a 737 8 Series, I mean it.
I’m in a tangential industry, but I can tell you from my observations and speaking with colleagues in the industry, this is only going to get worse. There is no impetus to make things better, and the can is only going to be kicked down the road. It seems like we are regressing as a species, and the more I read about history, the easier it is to understand how the dark ages came to be.
Mech Engineer/Comp Sci...THE INDIANS SUCK AS PROGRAMMERS AND AGAIN at Engineering...IF THE ANSWER ISN'T IN A BOOK SOMEWHERE or NOT PUBLISHED then the answer DOES NOT EXIST!!!!!!!
This story has been circulating for a while now. My view is that it is Boeing trying to point the finger elsewhere. Any developer does not do the whole job. Whan I used off-shore developer the customer wrote the initial spec. We analysts wrote the detailed spec. The developers coded it and we tested it as soon as it was complete.
You never expect any code to work so you have to catch the errors in your testing. After we (basically in-house IT) tested it the customer tested it as well. The testing usually took longer than the coding.
Blaming the developers for being less well off than you is hardly an excuse.
I worked for an indian tech firm. Every corner was cut and they lied about progress and deadlines. Just completely agreed to functionality they absolutely could not develop. I was told to hide defects during demos so we could meet milestones. Anything they actually released to UAT was just bug-riddled garbage and if you tried to send it back, they'd just argue that it's working fine.
The project was eventually shelved and the company sued for breach of contract. Nothing was actually delivered, but millions were wasted.
I guess it depends on how much of the job you sub-contract. My only experience is with off-shore coders. They realeased nothing directly to UAT (User Acceptance Testing). They installed the code on the development servers and we tested it there and only released it to UAT when we were happy.
However, I also worked in the aerospace industry and they take testing very seriously. Certainly, mechanical tests on components need to be carried out and the results kept for years in case faults develop in service.
I would have expected Boeing's testing, at UAT stage or elsewhere, should have found the issues. Whether they got them re-worked or whether, like you, they fired the developers, the bugs should not have made it into service.
That's easy to say but all software does have bugs!
I agree with your points, it's not so black & white. Also, from what I understand about the 737 MAX bug, it was extremely unlikely to happen and the result of a combination of factors.
Its a bit more complicated than that. There was mo system redundancy as with every other system because Boeing cheaped out on more than just software engineering....
Planes have been crashing long before any Indians got involved. These are complex systems that are over engineered and vulnerable to a million modes of failure. I'd say there is a systemic reliance on ever more automation that is more to blame than any individual workers. They make these planes practically fly themselves and sometimes they fly themselves into the ground.
Even fully maxed, you can't read 90% of it.
Was this image created by the same $9/hr Indian developers? Kek.
I think zooming helps. Instead of a big dark blur, I see a big light blur.
🤣🤣🤣🤣
The KEBOARD:
That just makes the blurry text larger. It doesn't help readability a bit.
You have to look at your device and say “zoom in and enhance”.
You probably forgot to say “enhance”.
Like the fake enhancement on CSI and NCIS?
What do you think fully maxed means? Good tips for people working with a proper image though.
And if you're on mobile, these instructions should read -
I flew right after 911, like the week after, knowing it would be the safest time to go (despite my family having nervous breakdowns). But afterwards, with all the "cost measures" put into place, especially those that bought into the magic math Indian myths, I stopped having faith in any programs that relied on transferring engineering or development to lower cost countries. This included ALL aerospace (remember all the air traffic control and ticket system failures?) and a lot of precision manufacturing. The facilities people and janitorial staff did not deserve the horrors perpetrated upon them. Haven't taken a plane in over a decade, would have been longer but family needs prevailed that time.
This some Biden-tier image quality
Is there a more readble verson of this? Most of the text is blurry.
I'm glad to know they were so focused on diversity, inclusion and balance.
Now... if they applied that same focus to AIRCRAFT PROGRAMMING, maybe the Boeing 737s wouldn't keep crashing.
Crashing is a part of diversity, it wouldn't be fair if all the planes flew successfully.
Now there is balance: some planes fly, some planes crash :)))
Incredible what they are trying to do.
Right? We've achieved so much pROgrEsS :::)
Boeing was under great pressure to produce a competitor for the Airbus A220 but the only airframe they had that could do that was the 737, they had to do this quickly to have any sort of chance to compete.
They cut corners in planning, tooling, tech authoring and configuration, these were savage cuts which the senior maintainers and engineers warned would lead to accidents. On top of this they wont woke as this post shows, Don't fly in a 737 8 Series, I mean it.
I’m in a tangential industry, but I can tell you from my observations and speaking with colleagues in the industry, this is only going to get worse. There is no impetus to make things better, and the can is only going to be kicked down the road. It seems like we are regressing as a species, and the more I read about history, the easier it is to understand how the dark ages came to be.
I don't think their decision had as much to do with going woke as it did to going cheap.
Barti Sharma,
The planes keep crashing. Please do the needful.
Thank you. Mr. Pareet Boeing PM
Street shitters....
Chemical industry has been using Indian engineers. Hope you are not down wind when they let go!
Mech Engineer/Comp Sci...THE INDIANS SUCK AS PROGRAMMERS AND AGAIN at Engineering...IF THE ANSWER ISN'T IN A BOOK SOMEWHERE or NOT PUBLISHED then the answer DOES NOT EXIST!!!!!!!
WOWZA!!!!!!!!🧨🧨🧨🧨🧨🧨
Good ol Jim Stone nailed this one a long time ago. It amazes me how He manages to have accurate info.
jimstoneindia
Add www and com after that. Don't let the address scare ya off, he had to setup multiple servers, tptb try shutting him down daily.
Carry On!!
This story has been circulating for a while now. My view is that it is Boeing trying to point the finger elsewhere. Any developer does not do the whole job. Whan I used off-shore developer the customer wrote the initial spec. We analysts wrote the detailed spec. The developers coded it and we tested it as soon as it was complete.
You never expect any code to work so you have to catch the errors in your testing. After we (basically in-house IT) tested it the customer tested it as well. The testing usually took longer than the coding.
Blaming the developers for being less well off than you is hardly an excuse.
I worked for an indian tech firm. Every corner was cut and they lied about progress and deadlines. Just completely agreed to functionality they absolutely could not develop. I was told to hide defects during demos so we could meet milestones. Anything they actually released to UAT was just bug-riddled garbage and if you tried to send it back, they'd just argue that it's working fine.
The project was eventually shelved and the company sued for breach of contract. Nothing was actually delivered, but millions were wasted.
Sounds about right.
I guess it depends on how much of the job you sub-contract. My only experience is with off-shore coders. They realeased nothing directly to UAT (User Acceptance Testing). They installed the code on the development servers and we tested it there and only released it to UAT when we were happy.
However, I also worked in the aerospace industry and they take testing very seriously. Certainly, mechanical tests on components need to be carried out and the results kept for years in case faults develop in service.
I would have expected Boeing's testing, at UAT stage or elsewhere, should have found the issues. Whether they got them re-worked or whether, like you, they fired the developers, the bugs should not have made it into service.
That's easy to say but all software does have bugs!
I agree with your points, it's not so black & white. Also, from what I understand about the 737 MAX bug, it was extremely unlikely to happen and the result of a combination of factors.
To be fair, Sangeeta Mishra is pretty funny and attractive for a $9 code monkey.
Its a bit more complicated than that. There was mo system redundancy as with every other system because Boeing cheaped out on more than just software engineering....
Planes have been crashing long before any Indians got involved. These are complex systems that are over engineered and vulnerable to a million modes of failure. I'd say there is a systemic reliance on ever more automation that is more to blame than any individual workers. They make these planes practically fly themselves and sometimes they fly themselves into the ground.
Unreadable garbage. Redo, plz.
Next, your local electric utility company is going to hire electrical engineers from South Africa.
It’s time to start canning and jarring food again. With no electricity, deep freezers will be filled with rotten meat.