You only press the “Run” button after you finish coding and teaching a Friendly AI; which happens after the theory has been worked out; which happens after...
If I had concrete ideas about how to make a strong AI, I’d start coding them at once. I’d only worry about Friendliness if and when what I’d actually built worked well enough to make this a serious question. Irresponsible? Maybe. But thinking out the entire theory before attempting implementation has no chance of producing any sort of AI. Look at the rivers of ink that have already been expended (Ben Goertzel’s books, for example).
Working out the theory first is substituting an easy problem for a hard problem, and the rivers of ink are just another way of going crazy.
This sounds like the Waterfall model of software development, which is not well thought of these days.
If I had concrete ideas about how to make a strong AI, I’d start coding them at once. I’d only worry about Friendliness if and when what I’d actually built worked well enough to make this a serious question. Irresponsible? Maybe. But thinking out the entire theory before attempting implementation has no chance of producing any sort of AI. Look at the rivers of ink that have already been expended (Ben Goertzel’s books, for example).
Working out the theory first is substituting an easy problem for a hard problem, and the rivers of ink are just another way of going crazy.