Comment For IT Jobs? (Score 1) 187
You'd think one company could come along and do everything just slightly better and blow all their competition out of the water, but so far this hasn't happened.
You'd think one company could come along and do everything just slightly better and blow all their competition out of the water, but so far this hasn't happened.
If you wanted to offer a bunch of different services in one location, something like that might work. But you'd still want to build a custom satellite rather than a modular system, because getting mass into orbit is very expensive, so no one's going to want to launch any more of it than absolutely necessary. The infrastructure for a modular system would be an unnecessary cost to launch hardware that might never actually get used.
Something like that might work for the geosynch satellites out in parking orbits after they reach their end of life, if it ever starts getting too cluttered out in that space. But people don't tend to care about what happens to the hardware in parking orbits. The story's Northrop project aims to extend the life of some of that hardware, but it still has to be in reasonable working order. Most of the satellites that would need something like that would by that time have been in space for a decade or so and are expected to start malfunctioning due to the radiation. So while this is a neat accomplishment, I expect it to be somewhat rare.
It could make sense to have a satellite manufacturing lab out there somewhere, though. If you can build them in space, it'd cost a lot less to move them to the correct orbit afterward. But you'd have to make your own fuel at that location, otherwise the cost of launching fuel to the lab (to fuel the satellites they would be building there) would be greater than the cost of launching all those satellites individually.
Space stuff gets done the way it gets done because it's the least expensive way to accomplish those goals. When you're talking hundreds of millions of dollars per launch, the least expensive option is always going to get chosen.
Also, keep in mind that the USA elected someone who was immediately clearly unfit for office. Even if we didn't vote for him, personally, we obviously didn't do enough to keep him out of office. We all should have donated more and volunteered for other campaigns. So honestly, we have no one to blame but ourselves and most definitely not him. This should in no way cause us to reevaluate the way our system works or is run. The pandemic is no time for thoughtful introspection or realizing that most of the world is handling it better than we are.
2. Apparently not. They'd just send it up a bunch of rotations to make, and it'd just make them at the appointed times.
3. Yah, ground systems was on Linux. At least some of their early satellites ran Windows, I'm not sure what the more recent ones did.
4. Oh yes, the satellites apparently had an atomic clock, same as the GPS satellites, IIRC. However, if the time coming from ground system said to make three specific rotations at a specific time, they'd just do it, and ground systems was a ridiculously complex set of systems designed by multiple teams, with no data validation or error handling between them.
5. I'm not really an expert on satellite hardware myself, but my understanding is that many satellites don't even have an OS, just dedicated hardware with code written right on the iron. Probably assembly or C. Or woven in, if you look at some of the early Apollo stuff. Some of their computers looked like knitting projects. You might see VxWorks, some variant of Windows and Linux on a few of them. Back in the heyday of the various commercial UNIXes, I imagine someone could have tried to license a UNIX to use. IBM was big on PowerPC for a while and I wouldn't be terribly surprised if AIX made it to space on some system or other.
Want some more? They knew their entire process was crap and couldn't bring new products to market in a reasonable timeframe. They adopted Agile something like three times while I was working for them, but they never gave anyone any time to get used to the process. They just kept throwing new processes at the problem every other month, to the point where developers just started ignoring them because the process being pushed this month would just be scrapped and replaced again in a month. They finally settled on getting their entire development team together off-site (A couple hundred people) for a week every quarter so that teams could work out what they needed to do in that quarter and badger the other teams into committing to do the work needed to support that. Oh yeah, good memories there.
Anywhoo, on behalf of that company, I'd like to say, please don't kidnap their employees. Anyone with half a brain left when they went public and anyone you could kidnap now would just set your country's space program back by a couple of decades.
The system was down for backups from 5am to 10am last Saturday.