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

I agree with your assessment, and I think in many ways one of the critical parts to learn is how to assess when it is ok to "turn off" the critical eye and be brash and confident and aggressive.

Some of my most valuable experiences stemmed from just throwing myself in on the deep end instead of waiting to analyze all the implications. But at the same time those experiences were terribly _hard_, and carried a great deal of risk. E.g. my first company was an ISP. Started it with some friends at 19. Knew nothing about running a business or about setting up a large scale WAN, or about accounting, or sales, or configuring Linux servers. A year later I'd had hard, brutal and effective lessons in all of that and more.

If I'd spent time carefully trying to figure out the risks and implications beforehand, I doubt I'd have started that company. It didn't make me wealthy, but it was definitively worth it in terms of what I learned, and the connections I made also led directly to my next job and overall it has been pretty vital to my career.

On the other hand, there are many situations where not stepping back and being careful and considered and chasing down the implications up-front would've had disastrous consequences.

The problem isn't being cautious, if you know when not to be, but not taking action. Being cautious because you want to chase down and understand the implications is very different from being timid about addressing weaknesses in your knowledge. Whether you address those weaknesses with research or by trying is less important than avoiding paralysis.



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

Search: