Not that I'm any authority, but I generally considering "knowing how to code" to require at least being able to use some sort of branching operation as well as some some sort of looping/recursion (which yes, is really just branching).
What you are talking about is a programming, although I do not understand how branching and recursion are the same. I am not aware of the way to express one by another.
> What you are talking about is a programming, although I do not understand how branching and recursion are the same. I am not aware of the way to express one by another.
I meant this at a really low level. Recursion is just a conditional jump and a stack push. When I said branching, I was thinking of the jump instructions in assembly (which allow you to jump to any point in a program, including instructions that have already been executed).
Perhaps Steve's greatest contribution to Apple was being its ultimate guinea pig. He wasn't an engineer, so he wasn't bogged down by the insecurities and fears and analytical thinking that plague the engineer's mind. He could "let go", as it were, and really evaluate the products coming out of his company for what they ARE, and their usefulness, unlike an engineer who always has the potential of making really geek-oriented products that fill a specific niche and aren't very useful outside that niche.