[chralieboy]

> Seeing a team build a prototype shows another level of commitment. I've built hardware, so i know how much more time/effort/money it takes over a software wireframe...

A wireframe is not the same as a hardware prototype. The similar analogy would be a functioning product, which in software is also difficult to do well. Functioning means it solves a need better than existing solutions, which requires research, experience, insight, and technical knowhow.

Furthermore, building a functioning software product that is well-engineered to scale (as opposed to a hacked out MVP) is, in my personal experience, rare. Very few "engineers" are able to.

[avidanr]

I agree. Perhaps using wireframes was not the best analogy. I studied computer science and spent quite a few years as a developer, both inheriting code bases, and building my own, so i do appreciate code thats built to scale! (though to be honest, mine rarely was...)