I think that question was included ironically- I.e., he's only been asked a handful of times. His sample size reflects the dearth of "learning how to program to

I think that question was included ironically- I.e., he's only been asked a handful of times. His sample size reflects the dearth of "learning how to program to build a viable webapp" stories and comments here. I don't even know if noob questions are accepted here- I've never seen one. I don't post them because I feel I should be finding answers on google rather than degrading the quality of this board. The decision to learn enough programming to build what I want stemmed from the realization that understanding how my webapp will work at the technical level significantly refines my vision for the product- bringing it much closer to reality. Whereas before I was talking to recommendation engine people because I wanted "recommendation features like Hunch," now I'm working in PHP/SQL and getting exactly what I want. My current strategy is to talk to the CTO's and creators of similar webapps to understand their technology and language choices (e.g. GAE or MAMP, SQL or Solr), go as far as I can on my own, and then work with a tutor for an hour or two to get momentum and correct my architecture mistakes.