Just Build the Product
This is the right advice if you want to nerd out on technology.   But my experience suggests[1] that if you want to build a <i></i>business<i></i> it'll be cheaper to validate problem/solution with phone calls and mocks / designs before writing code.<p>This is because:<p>* It's cheaper to make changes before code has been written<p>* A functioning product isn't the best sign that you're making progress - paying customers are[2]<p>Don't get me wrong. I like to write code as much as the next guy / gal.  But  I've made the mistake of writing code first.  And I've worked with clients  who - despite my best attempts - decided to forego validation to build a product that they spent a lot of dev dollars on to fix once the market met it with a trickle of interest.<p>1- <a href="https://uncog.com/archive/v2/why-only-fools-write-code-first/" rel="nofollow">https://uncog.com/archive/v2/why-only-fools-write-code-first...</a><p>2- <a href="https://uncog.com/archive/v2/how-to-get-paying-customers-before-you-start-writing-code/" rel="nofollow">https://uncog.com/archive/v2/how-to-get-paying-customers-bef...</a>