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

I've been on the other end of that story quite a few times - being the person having to point out that "this isn't going to work even for normal loads", and having people argue that caring about performance is "premature optimization". And then see them crash and burn because of the arrogance of not testing their assumptions before betting the farm on them.

I think the path of least conflict is usually to encourage people to develop quick benchmarks and test their assumptions and then ask questions about how they plan to address any problems that identify themselves. If people are receptive another useful piece of advice is that they shouldn't be afraid of just starting over if it is really early in the project.




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

Search: