4 ms·
Great. Should be easy to prove then.
by imron 4y ago
Great. Should be easy to prove then.
- dahfizz 4y agoYup, we have a good benchmarking suite to make sure changes don't cause regressions and that optimization changes actually work. That said, I think asking a developer to write everything they do twice so that they can A/B test is overboard. You can come back and really aggressively optimize later, but I think the "default" should be the fast thing, rather than the slow & easy thing.
- bmacho 4y agoIf "performance really does matter" (in Fintech) then a developer surely can write everything twice or more.
- dahfizz 4y agoWe could, yeah. I'm sure you're capable of re-writing everything you do twice. It's just a huge waste of time. You get just as much benefit by assigning a performance refactor to an engineer when needed vs literally halving or worse the whole teams productivity.
- gpderetta 4y agoTime to market can matter in fintech as much as anywhere else. Edit: also optimizations often interact with each other and you can't always benchmark all possible combinations, so sometime you do have to rely on experience or reasoning from first principles to decide if an optimisation is worth it or not.
- elimerl 4y agoThe idea is that the "default" is the easy thing, which is usually optimized by the compiler.
- TillE 4y agoWhen you're writing in a language like Rust or C++, you know broadly what the compiler optimizes and what it probably won't. You do need to do the work yourself a lot of the time.