3 ms·
1 year to talk to people in real businesses that aren't in tech and study their problem in depth. 4 years to create what they need. Too vague? I don't know en
by wheaties 14y ago
1 year to talk to people in real businesses that aren't in tech and study their problem in depth.
4 years to create what they need.
Too vague? I don't know enough about enough things outside of tech to really build something that would actually help the rest of the world. (The only thing I can think of is another Skype-like company akin to Twillio but for video communication with a phone. That probably would fail until costs come down.)
- rajesht 14y agothats a waterfall model, may be agile might be more useful :)
- hackerpolicy 14y agoAn interesting response, perhaps you're being downvoted for an English mistake?
- 31reasons 14y agoI really liked the idea that you added problem search as part of the product development. Many times investors want to invest in you if you already have the idea. It would be awesome to think some investment funds to just search for problems in specific domains!
- paulsamways 14y agoMore people should be doing this. You don't even have to move out of tech yourself, find a position in a company where tech is only ancillary, not the core focus. You'd be surprised just how many real problems are out there waiting to be solved.
- gpjt 14y agoYou can do that, but it might not be fun. I spent 4 years in tech at A Big Financial Company and the one thing I learned was that I didn't want to work at a company where my work wasn't a core part of the business. I've heard that at Oracle they say (used to say?) that you build [stuff], you sell [stuff], or you are [stuff].
- paulsamways 14y agoWon't disagree with you there! Though sometimes going outside your comfort zone can be a good thing.