The Customer Development Manifesto: Reasons for the Revolution (part 1)
1–3 of 3 posts
Re: The Customer Development Manifesto: Reasons for the Revolution (part 1)
#2Most startup code ends up on the floor.
Scary thought. I worked too hard to let this happen.
And it's a very easy trap to fall into. When I'm coding, I don't want to talk to customers. And when I'm talking to customers, I don't want to code. Gotta find a way to interweave them sensibly.
Re: The Customer Development Manifesto: Reasons for the Revolution (part 1)
#3Most startup code ends up on the floor. Scary thought. I worked too hard to let this happen. And it's a very easy trap to fall into. When I'm coding, I don't want to talk to customers. And when I'm talking to customers, I don't want to code. Gotta find a way to interweave them sensibly.
Sounds like you need to follow the maker/manager schedule described here http://www.paulgraham.com/makersschedule.html