Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> when you're constructing something original, you can't communicate it to someone completely because there are always too many details, even things you haven't resolved yet yourself.

This is what's so hard to explain to people.

It's the necessary, painful part of any project: where you get to the part that you may not know exactly how to solve. A more communal individual would be prone to throw their hands up and call for a meeting. (I hate when people try to make their problems be everyone's problems.) But, they're cheating themselves out of a wonderful experience. Going at it alone in the face of uncertainty is a delicious thrill; you start hacking away at it, hoping for something to give, but ultimately knowing you're just making it up as you go, and it may not work out. Eventually, you learn enough about the problem such that you can talk about it semi-coherently. But until then, talk is useless, no, it is an impediment. Without understanding, there is no use attempting to articulate anything. Intuition begets understanding.

I believe some companies simply cannot accept this level of uncertainty. It's too dangerous to take something on that might fail. They can hire all the cogs they want.



I feel what you're putting down. It is very hard to explain to people what it is like when you are at the point of a project where you are not really even looking for answers yet. No, you're still determining what the questions are. You're still figuring out what the "what" is. They just don't get it, but I really think you have to go through that to produce a useful product.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: