Hacker News new | past | comments | ask | show | jobs | submit login

I think it's the right approach, as long as you realize you won't be able to think of everything up front, and don't let that thought be a burden.



Simply being aware that there exist things that you don't know you don't know can save your project.

This is the general basis for why I tend to pick tools & concepts that are at least a half-decade old. The space of unknown unknowns in something that has been around this long should be vanishingly-small, especially if we are applying the tool or concept in a typical way.


But definitely give it some times to think of it upfront. Weight them by 2 factor: severity and frequency. Then try to tackle as much as you can from the top list of severity * frequency level.


> You have to think your optimization approach from the other end, as how it might fail.




Join us for AI Startup School this June 16-17 in San Francisco!

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

Search: