Slashdot Mirror
X Prize and John Carmack
Anonymous Coward writes "ABC News is running a story ostensibly about the X Prize but in reality they only talk about John Carmack and his teams efforts to win the prize (or at least compete). Quote: 'Some people have commented that I am trying very hard to make aerospace like software, and that's the truth," he says. "If we looked at what we do in software, if we could only compile and test our program once a year, we'd never get anything done. But that's the mode of aerospace.' "
I read the internet for the articles.
While mass-producing a learjet probably doesn't cost much at all, building the first prototype probably cost many 10s of millions in development costs. If this team is building a prototype for $1-2 million and that includes all material, development and testing costs, I'm definitely not buying a house in its flight-path.
Yeah, there's a world of difference between buying a personal jet from a private company that must be flightworthy for dozens or hundreds of flights a year and comply with acres of FAA regulations before they even get off the ground. Not to mention the high markup on those jets.
These rockets are being built with more or less volunteer time and by people who are willing to scrounge for parts and look long and hard for bargains. I think you'd find that the raw materials that go into a Learjet aren't all that expensive (steel by the pound, etc...), but the labor costs, health plans, salespeople comissions, buildings, paperclips, etc... add considerably to the cost of the final product.
I read the internet for the articles.
Duh.
.sigs are for post^Hers.
If you know how, and count your time as "valueless," you can build a hang glider for. . . nothing.
You can build a sports car that rivals a Corvette and get it road certified for only a few grand, even though a new Corvette costs a damned sight more than that.
Most of the expense of doing things, even making video games, comes from doing things in a standard way inside of a standardize buearacratic system.
Throw out the red tape, open your mind to alternative ways of accomplishing the same goals, work for the joy of it and eliminate the market as motivator and you might surprised at how much you can accomplish with relatively little cash.
Watch a few episodes of Rough Science.
KFG
For spaceflight, we need people who think like the old school programmers. The ones that actually planned their programs before they wrote them. When it took twenty-four hours (or more) between when you submitted your card deck and when you got your output (or a core dump) you learned to be damned careful with your code. The modern attitude of "keep tweaking it until it compiles; we'll fix the bugs in 2.0" won't wash in spaceflight.
~Idarubicin
The tricky part is that I don't think tests done with small rockets will necessarily give you a good idea of how the big rocket will perform. If that were the case, all we'd really need is to buy a model rocket kit from Wal-Mart and just build it 20x bigger.
You call it a holy war, I call it English. The English language is being eroded gradually by ignorance.
There's a reason for having two words, then and than. It's preferrable to have exact words that aren't dependent upon context. If we just toss out "than", and exclusively use "then", our language will become even less precise.
Some other common mistakes that really suck:
confusing "your" with "you're"
confusing "their" with "they're"
adding unnecessary apostrophes to plural words - Dog's and Cat's...
Just because some people have forgotten or were never taught how to write the language they speak doesn't mean that we should just dumb it down completely. Taken to the extreme, we could just back all the way up to grunts and growls.
.sigs are for post^Hers.
Software developers have learned that the Waterfall model *doesn't work* because it's too slow, expensive, and inflexible. Sound like any space programs you know?
There is a continum between experimentation and analysis. So long as space is dominated by risk-averse govt. bureaucracies, your vision of space exploration will continue to slowly plod along. But remember when the real progress happened: in the 60s, when rockets blew up quite often. The consequence of a failed unmanned flight is only financial, and that means failure can be justified by overall savings.
You probably mean "Burt Rutan", the aircraft designer at Scaled. Dick Rutan is his brother, who piloted the voyager, and was the test pilot for XCOR's EZ-Rocket, but doesn't have anything to do with Space Ship One, the X-Prize vehicle.
I have always maintained that Burt is the odds-on favorite to win the X-Prize, but it isn't over yet. His design requires a pilot on board for all tests, so there is a non-negligable chance that there could be a fatality, which would almost certainly end the effort in the X-Prize timeframe.
John Carmack
I see a lot of skeptics replying, "Carmack is wrong headed, if you screw up a rocket, it crashes, it's not just a compile bug". Many of these comments seem to be suggesting that we should go back to the "old school" style of programmer that thought & planned his code before submitting, instead of relying on the feedback of a compiler.
This is based on the completely false assertion that code will be better / more bug free if you "think harder". It ignores that in the past 30 years of programming we have learned the value of feedback in the software development thought process.
The idea that somehow if I spend more time in a chair planning the solution that the solution will be better if I evolve my way to it is some sort of romantic vision of how solutions to tough problems are actually solved. This could be seen as a version the "prove the code works" vs. "test the code" debate. Or that proofs follow from the axioms. I counter that usually it's a process of some rather messy creativity, trial, and error.
In programming in the large, we have generally learned that "phased" approaches to software development (known as waterfall) tend not to work very well because they de-emphasize the feedback that occurs downstream in the development process. To contrast, an incremental approach enables smaller steps to be delivered , and minimizes the impact of erroneous assumptions discovered downstream in the development.
In programming in the small, development is a form of communication between the computer and the developer. The computer is designed to tell us where we are wrong, we just need to tell it exactly what to expect: for this we have compilers and test cases. Compilers can't catch everything.
Now, this is not suggesting that today's style of "let's see if it compiles!" development is appropriate for aerospace. That is the unfortunate effect of feedback & incremental approaches - it makes programming easier, even for people that shouldn't be doing it. These people "program by accident", and just meander through their code until it does the job, sort of. This is not a reflection of the incremental approach in the hands of an experienced developer that "programs on purpose", that understands what he or she is doing at every step of the way.
Aerospace development isn't "amateur hour", and the incremental approach will just make professionals all the more productive.
-Stu