3 ms·
This is better expressed as "consider performance from the start". Don't make it your #1 priority and don't ignore and neglect it either. Do sensible things: 1
by karmakaze 7y ago
This is better expressed as "consider performance from the start". Don't make it your #1 priority and don't ignore and neglect it either. Do sensible things:
1. use hash (or ordered) collections rather than scanning large-ish arrays
2. use reasonable database schemas and indices for queries
3. similarly consider correctness (e.g. constraints)
4. one place where earlier versions can skimp are sometimes algorithms to be replaced by better ones. Think of this as 'doing things that don't scale' which is fine for an MVP but do have a plan for how this will be updated if you're fortunate enough to need it.
5. good fore-thought is to offload work to the client in the design which does scale better.
6. don't do any/much caching early on and make choices that are compatible with adding caching later