![](https://lemmy.deadca.de/api/v3/image_proxy?url=https%3A%2F%2Flemmy.world%2Fpictrs%2Fimage%2F266a4de3-4c21-4b08-a207-1cf32ea1cc00.png)
![](https://lemmy.deadca.de/api/v3/image_proxy?url=https%3A%2F%2Flemmy.one%2Fpictrs%2Fimage%2F0f5e05b5-d351-4add-9667-1df4c43091b4.png)
What are you talking about?
What are you talking about?
It’s still surreal to see OpenAI’s need for training data be so vast that they casually developed and open sourced a generational leap in transcription technology just so that they could scrape online videos better.
The Hard Fork podcast had a pretty good episode recently where they interviewed one of the engineers on the project. They’d troubleshooted the spacecraft enough in the past that they weren’t starting from square one, but it still sounded pretty difficult.
Modern satellites are protected by various means of encryption, but there’s an enthusiast community that tracks down and communicates with very old unencrypted zombie satellites. There’s even been an NGO which managed to fire rockets on an abandoned NASA/ESA probe (with their approval.)
The Voyagers benefits primarily from the lack of groups with an adequate deep space network to communicate with it. Their communication standards are otherwise completely open and well documented.
I still cannot believe NASA managed to re-establish a connection with Voyager 1.
That scene from The Martian where JPL had a hardware copy of Pathfinder on Earth? That’s not apocryphal. NASA keeps a lot of engineering models around for a variety of purposes including this sort of hardware troubleshooting.
It’s a practice they started after Voyager. They shot that patch off into space based off of old documentation, blueprints, and internal memos.
Zac Gorman’s comic with the original dialog: https://magicalgametime.com/post/48470399171
The two hardest problems in computer science are cache invalidation, naming things, and off by one errors.
My favorite compile error happened while I was taking a Haskell class.
ghc: panic! (the ‘impossible’ happened)
The issue is plainly stated, and it provides clear next steps to the developer.
My favorite one of these shows up in 3D printing. The most popular open source 3D print server gives you a head’s up if your printer’s firmware lacks “Thermal Runaway Protection”. If you click the learn more link, it patiently explains, “There aren’t preventative measures to stop your printer from accidentally catching itself on fire”.
(It’s fine, you usually just need to install a decent MOSFET in the cheaper printers.)
If you’re looking for a new Jet Set Radio style game, make sure to check out the recently released indie project Bomb Rush Cyberfunk. They did a great job of capturing the JSR spirit while modernizing the controls and gameplay. https://store.steampowered.com/app/1353230/Bomb_Rush_Cyberfunk/
“My battery is low and it’s getting dark.”