Skip to main content

After 53 Years, a Failed Soviet Venus Spacecraft Is Crashing Back to Earth

11 hours 52 minutes ago
Kosmos 482, a failed Soviet Venus probe, is expected to make an uncontrolled reentry in mid-May after orbiting Earth for 53 years. Gizmodo reports: The lander module from an old Soviet spacecraft is expected to reenter Earth's atmosphere during the second week of May, according to Marco Langbroek, a satellite tracker based in Leiden, the Netherlands. "As this is a lander that was designed to survive passage through the Venus atmosphere, it is possible that it will survive reentry through the Earth atmosphere intact, and impact intact," Langbroek wrote in a blog update. "The risks involved are not particularly high, but not zero." Kosmos 482 launched on March 31, 1972 from the Baikonur Cosmodrome spaceport in Kazakhstan. The mission was an attempt by the Soviet space program to reach Venus, but it failed to gain enough velocity to enter a transfer trajectory toward the scorching-hot planet. A malfunction resulted in an engine burn that wasn't sufficient to reach Venus' orbit and left the spacecraft in an elliptical Earth orbit, according to NASA. The spacecraft broke apart into four different pieces, with two of the smaller fragments reentering over Ashburton, New Zealand, two days after launch. Meanwhile, two remaining pieces, believed to be the payload and the detached upper-stage engine unit, entered a higher orbit measuring 130 by 6,089 miles (210 by 9,800 kilometers). The failed mission consisted of a carrier bus and a lander probe, which together form a spherical pressure vessel weighing more than 1,000 pounds (495 kilograms). Considering its mass, "risks are similar to that of a meteorite impact," Langbroek wrote. As of now, it's hard to determine exactly when the spacecraft will reenter. Langbroek estimates that the reentry will take place on May 10, but a more precise date will get clearer as the reentry date nears.

Read more of this story at Slashdot.

BeauHD

CodeSOD: Find the First Function to Cut

12 hours 22 minutes ago

Sebastian is now maintaining a huge framework which, in his words, "could easily be reduced in size by 50%", especially because many of the methods in it are reinvented wheels that are already provided by .NET and specifically LINQ.

For example, if you want the first item in a collection, LINQ lets you call First() or FirstOrDefault() on any collection. The latter option makes handling empty collections easier. But someone decided to reinvent that wheel, and like so many reinvented wheels, it's worse.

public static LoggingRule FindFirst (this IEnumerable<LoggingRule> rules, Func<LoggingRule, bool> predicate) { foreach (LoggingRule rule in rules) { return rule; } return null; }

This function takes a list of logging rules and a function to filter the logging rules, starts a for loop to iterate over the list, and then simply returns the first element in the list, thus exiting the for loop. If the loop doesn't contain any elements, we return null.

From the signature, I'd expect this function to do filtering, but it clearly doesn't. It just returns the first element, period. And again, there's already a built-in function for that. I don't know why this is exists, but I especially dislike that it's so misleading.

There's only one positive to say about this: if you did want to reduce the size of the framework by 50%, it's easy to see where I'd start.

[Advertisement] BuildMaster allows you to create a self-service release management platform that allows different teams to manage their applications. Explore how!
Remy Porter

How to survive as a CISO aka 'chief scapegoat officer'

13 hours 20 minutes ago
Whistleblowing, email is evidential mail, HR is not your friend, and more discussed by CxO panel

RSAC  Chief security officers should negotiate personal liability insurance and a golden parachute when they start a new job – in case things go sideways and management tries to scapegoat them for a network breach.…

Iain Thomson