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

I'd probably swap them:

1. Make it work.

2. Make it not break.

3. Make it manageable.

4. Make it fast.

Otherwise I find that trying to make something fast before making it manageable usually ends up in crazy hacks that are hard to undo later.



3.5 Profile it to see whether or not it needs to be faster


If you profile it on a fast machine, your results might lie to you.


Or on a machine on a fast network, or SSD vs spinning-rust, or any number of varying factors.


I'd agree with this. My last couple of projects did have a couple of hacks that bordered on spaghetti code until they were sufficiently cleaned up.


It's less likely to break if it's manageable first.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

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

Search: