3 ms·

4. Make it manageable.

• ianstormtaylor 10y ago
  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.
  • ogreveins 10y ago
    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.
  • stevetrewick 10y ago
    3.5 Profile it to see whether or not it needs to be faster
    • voltagex_ 10y ago
      If you profile it on a fast machine, your results might lie to you.
      • douche 10y ago
        Or on a machine on a fast network, or SSD vs spinning-rust, or any number of varying factors.
  • gohrt 10y ago
    It's less likely to break if it's manageable first.