4 ms·
How are you supposed to know though, when your code is doing better then 'it works'?
by biz2hack 17y ago
How are you supposed to know though, when your code is doing better then 'it works'?
- mbrubeck 17y agoIt's efficient. It's concise. It's easy for you to understand and modify. It's easy for others to understand and modify. Over the long term, it proves to have a low defect rate. It's declarative, and lends itself to automatic optimization.