Slashdot Mirror
Russia Thinks Someone With a Drill Caused the Recent ISS Air Leak (arstechnica.com)
Last week, NASA discovered a small pressure leak on the International Space Station. U.S. and Russian crew members managed to trace the leak to a 2mm breach in the orbital module of the Soyuz MS-09 vehicle and patch it with epoxy. The drama might have ended there, as it was initially presumed that the breach had been caused by a tiny bit of orbital debris, but Russian news outlets are reporting that the problem was a manufacturing defect. "It remains unclear whether the hole was an accidental error or intentional," reports Ars Technica. "There is evidence that a technician saw the drilling mistake and covered the hole with glue, which prevented the problem from being detected during a vacuum test."
"We are able to narrow down the cause to a technological mistake of a technician. We can see the mark where the drill bit slid along the surface of the hull," Dmitry Rogozin, head of the Russian space agency Roscosmos, told RIA Novosti. "We want to find out the full name of who is at fault -- and we will." From the report: NASA spokesman Dan Huot, based in Houston where the space station program is managed, deferred all comment on the issue to Roscosmos. The spacecraft was manufactured by Energia, a Russian corporation. A former employee of the company who is now a professor at Moscow State University told another Russian publication that these kinds of incidents have occurred before at Energia. "I have conducted investigations of all kinds of spacecraft, and after landing, we discovered a hole drilled completely through the hull of a re-entry module," the former Energia employee, Viktor Minenko, said in Gazeta.RU. "But the technician didn't report the defect to anyone but sealed up the hole with epoxy. We found the person, and after a commotion he was terminated," said Minenko. In this case, the technician used glue instead of epoxy. As the Soyuz hull is made from an aluminum alloy, it could have been properly repaired on Earth by welding, had the technician reported the mistake.
"We are able to narrow down the cause to a technological mistake of a technician. We can see the mark where the drill bit slid along the surface of the hull," Dmitry Rogozin, head of the Russian space agency Roscosmos, told RIA Novosti. "We want to find out the full name of who is at fault -- and we will." From the report: NASA spokesman Dan Huot, based in Houston where the space station program is managed, deferred all comment on the issue to Roscosmos. The spacecraft was manufactured by Energia, a Russian corporation. A former employee of the company who is now a professor at Moscow State University told another Russian publication that these kinds of incidents have occurred before at Energia. "I have conducted investigations of all kinds of spacecraft, and after landing, we discovered a hole drilled completely through the hull of a re-entry module," the former Energia employee, Viktor Minenko, said in Gazeta.RU. "But the technician didn't report the defect to anyone but sealed up the hole with epoxy. We found the person, and after a commotion he was terminated," said Minenko. In this case, the technician used glue instead of epoxy. As the Soyuz hull is made from an aluminum alloy, it could have been properly repaired on Earth by welding, had the technician reported the mistake.
I am pretty sure that terminated in Russia is not a good thing.
It's funny how I make sense to others and not myself...
The reason there are issues because people fear losing their jobs if they report a mistake of their own doing. It happens at some companies that don't realize that a mistake is part of normal business operations and thusly an expected cost.
They should find the person that did this and interview him and then hold his management responsible.
"Dmitry Rogozin, head of the Russian space agency Roscosmos, told RIA Novost "We want to find out the full name of who is at fault -- and we will."
Facepalm! Dmitry Rogozin is at fault, you nitwit.
The problem is that the workers were afraid to admit a mistake and get it fixed - to the point that they'd rather jeopardize the mission by hiding the mistake than acknowledge an error. So this jackass responds with "we will find out the full name of the person [and then ...]". That attitude IS the problem, dummy. To fix the problem, your statement would need to be "we want to find out why workers are afraid to acknowledge errors and fix the organizational culture so that errors can be acknowledged and fixed properly, rather than hidden."
Old joke: Wealthy merchant tells man he can marry his daughter if he manages to do 3 things:
1. Drink a full bottle of vodka
2. Wrestle a bear to the ground
3. Fuck his grandma
He downs the bottle, heads into the bear den and after half an hour of screams and battle sounds, he emerges with scratches all over, yelling "Ok, where's the hag I have to fight with?"
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
As a Finn with a couple Russian friends who've left their country because of 'organisational culture' let me give you some perspective. This is Putin's ' Novorossiya' where transparency is nonexistent and those who fail to satisfy the powers that be are thrown into jail in the best case, get into mysterious accidents or commit 'suicides' in the worst case. The space program is a key component in the cold war (which never really ended, it's just changed its nature to be less about armed conflict and more about information warfare) propaganda just as it was in the past, and as such it is of great importance to Kremlin. Whoever made the mistake is not afraid of getting fired, because getting fired is the least of your concerns in this situation. If I were him, I'd already be on my way out of the country and never drink any tea I haven't prepared myself..
The problem is not the the organisational culture of Roscosmos, the problem is the organisational culture of the entire State Meet the new boss, same as the old boss:
"Enemies are right in front of you, you are at war with them, then you make an armistice with them, and all is clear. A traitor must be destroyed, crushed."
-Vladimir Vladimirovich Putin in 2001, speaking to journalist Aleksei Venediktov, to whom he added “You know, Aleksei, you are not a traitor. You are an enemy.” (source: David Remnick, “Echo in the Dark,” in The New Yorker, September 22, 2008)
This is why seeing Trump act like Vlad's obedient little lapdog earlier in the summer here in Helsinki was one of the most absurd things I have ever witnessed in my life. Had you told me ten years ago that you're from the future where the fucking president of the US of A bows down to kiss the ring of Putin and call the European Union a foe, I'd have told you to go get your head checked. Yet here we are. My grandfather who's in his 80s said to me after the press conference that he thinks the Russians are winning, because 'one of the guys is a former KGB agent, and the other is a clueless goof.' Although grandpa is no political scientist, I have a hard time disagreeing with him here.
"It is the business of the future to be dangerous" -Alfred North Whitehead
Which one do you think is better:
1. Ensure zero mistakes are made, by punishing people who make mistakes, and by other means, or
2. Create a culture where mistakes that are made are correctly reported and dealt with?
Hint: The first one is not possible, because perfection is impossible.
The mistakes should of course be minimized, and intentional incorrect actions, like sabotage, should of course be punished. Of course, you can argue that not reporting a mistake is an intentional incorrect action, but this could be avoided by choosing wisely how mistakes are dealt with. So paradoxally, trying to push for zero mistakes by punishment, you're actually 1) not necessarily reducing mistakes, and 2) additionally causing intentional incorrect actions, thus making the situation worse. If you're a manager, I hope you take some time to consider this.
People make mistakes all the time. The only person who makes no mistakes is a person who does nothing.
So if you punish mistakes, the solution people will come up with is to do nothing. Which will make finishing a project also completely impossible.
Ahahahah... You know Ivan, your propaganda shitposting would be far more effective if your Finnish didn't sound like it came from a 40s black and white movie (no-one in modern Finnish uses the words 'sinjoore' or 'madame' for example) and riddled with typos (you're missing almost every single ä and ö there, and ryssä is written with a y and not a ü which is not even used in the entire language at all you dimwit).
But ladies and gentlemen of Slashdot: if you had any doubts prior to this point that the Russian trollboys are patrolling this site actively, I give you exhibit A: a dude writing about the Clintons in archaic and misspelled Finnish that clearly does not come through Google translate to try and pass as a native..I mean, A for effort, F for execution man.
These guys reply to me as ACs almost every single time I mention Putin in any way here, it's almost kinda endearing, like having a sort of pet. You know Ivan, I don't blame you. Work is hard to find in the current shit economy of Russia, and at least you get an indoors work-environment, hopefully decent pay and bonus points for being an obedient little trooper in the Motherlands fight against 'The West. If you ever end up in here, we can go and have a cup of coffee or tea, and don't worry, I'll bring my own Geiger counter. ;)
Until we meet again, comrade!
"It is the business of the future to be dangerous" -Alfred North Whitehead
You know how Russia ended up with Putin? Remember Yeltsin? Remember how we interfered with the 1996 Russian election and altered the result? Yeltsin was in the single digits before the Americans got involved.
You know what happened next? The US financial "experts" pushed Yeltsin to introduce neo-liberal shock therapy economics to the new Russian Federation. Ended up crashing the economy and leaving more in poverty then ever before. The number of people living in poverty in the former Soviet Republics rose from 14 million in 1989 to 147 million in 1998. As a result of the 1998 financial collapse and the devaluation of the ruble, the life savings of tens of millions of Russian families disappeared overnight. In the period from 1992 to 1998 Russia's GDP fell by half - something that did not happen even under during the German invasion in the Second World War.
Under Yeltsin's tenure, the death rate in Russia reached wartime levels. Accidents, food poisoning, exposure, heart attacks, lack of access to basic healthcare, and an epidemic of suicides - they all played a role. David Satter, a senior fellow at the anti-communist, Washington DC-based Hudson Institute, writing in the conservative Wall Street Journal, described the consequences of this victory of Democracy: "Western and Russian demographers now agree that between 1992 and 2000, the number of 'surplus deaths' in Russia - deaths that cannot be explained on the basis of previous trends - was between five and six million persons."
This secured Putin as a savior to Russians when he reversed it, and soured Russian public opinion to the US.
Shutting down free speech with violence isn't fighting fascism. It IS fascism!
In general this is quite true.
In jobs where perfections is demanded, problem occur, because people are afraid to report mistakes. Often these mistakes could had happened to anyone, but that one guy was the one who did it that day. However they will get fired for making that mistake without learning from it and will need to fire the next guy.
So being the problem isn't fixed, and you could get fired with one off action that lasted less then a second. If you messed up, you are not going to report the problem. you will probably just patch it up, and continue on.
I do a lot of Database work. Sometimes I mess up on my delete command. Now experience has taught me to have a plan for when I mess up. But I still mess up. And others that work with have done the same thing. Now I have some Jr developers on my team, they go into panic the first time that happens. Other then yelling at them, or giving them a hard time, I will work with them to recover as much data as possible and work on getting the data in place. After the experience they are less likely to make the same mistake, and they are better now knowing how to retrieve from backup and make preemptive backups beforehand.
Now if they keep on messing up and deleting the data after going via the process over again. Then I will get tough on them. Making a mistake is fine, making the same mistake over and over again isn't, especially if there are things you can do to stop it.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
Or he may had reported it, and his manager told him to patch it up. But being no paperwork when the problem happened, the fingers got pointed down until there was no one left to point too.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
Defense from who? NATO destroyed Libya, and some of it's member nations were behind the destructions of Syria, Iraq and Afghanistan. It's the rest of the world that needs defense from the United States and its poodles, not the other way around.
I call them "trade partners". I also call people who regard a trade deficit as "ripping off" "abyssmally ignorant of the basic facts of economics." A trade deficit is when a country sends us more good then we send them--for which they take dollars that *we print*. This is bad?
> Now if they keep on messing up and deleting the data after going via the process over again. Then I will get tough on them. Making a mistake is fine, making the same mistake over and over again isn't
This is the correct way to do things. One of the things I do with a junior who makes a mistake is have them fix it with a bit of guidance, but with them doing the actual work. I find that approach helps people become more careful - they're less likely to carelessly screw something up if they've already gone through all the work it takes to fix it. One particular example springs to mind of a linux server in a QA environment - pre VM days - and a junior mistakenly chmodded everything recursively from / . We could have rebuilt the server and restored backups, but I thought it would be a better lesson to have them fix all the permissions by hand. It took said junior most of the day, but after that they became obsessive about triple and quadruple checking anything they were doing with elevated privileges and they never made that mistake ever again, or any other comparable mistake.