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

Generally speaking I don't. The only way I've ever been able to be successful on the performance front is to conclude that code that is slow is broken, not that it is working before then.

Backing into acceptable performance after the fact just doesn't work for the problem domains I work in (which on first blush have not been exclusively performance based).




If your attitude is shaped by narrow problem domains, why argue with people as if you were talking about the general case?




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

Search: