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

All I said is you identify the major factor first and fix it, and keep doing that. What you're saying now is basically what I started with, except applying a recursive step of "keep identifying new bottlenecks". But the algorithm should always be "Look at the biggest factor and nothing else", of course you should check if the biggest factor stays the same over time



Consider applying for YC's Summer 2025 batch! Applications are open till May 13

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

Search: