I believe I went with the wrong interpretation of “solve”. I read it as something much more open, in the sense of “figuring out the problem’s key elements”, which would mean “needing to solve” google-scale projects and then them being “reasonable to solve” is equivalent to doing the research and experimentation required to figure out all the important structural elements of the problem, and what kind of team exactly would be working on which problems in order to implement the full solution.
If I interpret “solve” as in “fully functional” (coded, runs, performs the desired operation without bugging for the standard test cases), then what you said and what I said reduce to approximately the same thing.
I’m pretty sure we exactly agree on this. Just out of curiosity, what did you think I meant?
I believe I went with the wrong interpretation of “solve”. I read it as something much more open, in the sense of “figuring out the problem’s key elements”, which would mean “needing to solve” google-scale projects and then them being “reasonable to solve” is equivalent to doing the research and experimentation required to figure out all the important structural elements of the problem, and what kind of team exactly would be working on which problems in order to implement the full solution.
If I interpret “solve” as in “fully functional” (coded, runs, performs the desired operation without bugging for the standard test cases), then what you said and what I said reduce to approximately the same thing.