So I guess the main point of this article was to get some ideas down and provide a quick summary of things I've learnt in the past year. Getting feedback is helpful as it shows where I can drill down in to more detail in future posts.
For now quick responses to your points:
1. We spent a lot of time playing around with ideas, thinking big, making assumptions about what people wanted. We should have just built something small, quickly, put it out there and got feedback. Basically build a smaller MVP.
2. Knowing the basics is a good place to start - it at least makes it easier to hire the right people if you understand the role a bit.
3. Agree with your counter point. Specifically we spent a lot of time agonising over Rails or Django - when for our project there wouldn't have been much difference between the two - either would have been just as good. Getting the MVP built would have been a more constructive use of time.
Comments
So I guess the main point of this article was to get some ideas down and provide a quick summary of things I've learnt in the past year. Getting feedback is helpful as it shows where I can drill down in to more detail in future posts.
For now quick responses to your points:
1. We spent a lot of time playing around with ideas, thinking big, making assumptions about what people wanted. We should have just built something small, quickly, put it out there and got feedback. Basically build a smaller MVP.
2. Knowing the basics is a good place to start - it at least makes it easier to hire the right people if you understand the role a bit.
3. Agree with your counter point. Specifically we spent a lot of time agonising over Rails or Django - when for our project there wouldn't have been much difference between the two - either would have been just as good. Getting the MVP built would have been a more constructive use of time.