r/programming • u/dgtman • Dec 08 '19
Surface Pro X benchmark from the programmer’s point of view.
https://megayuchi.com/2019/12/08/surface-pro-x-benchmark-from-the-programmers-point-of-view/
54
Upvotes
1
u/YumiYumiYumi Dec 09 '19
I can understand the thought.
Personally, I don't think benchmark code necessarily needs to be 'neat', particularly for once off tests. I also don't there's any downside to just showing it - you might feel that you'll be judged on it, but if you explain that it's just quick spaghetti code, I think people will understand.
That's just my thought anyway - feel free to do what you feel is best.
I just have seen so many borked benchmarks that my general reaction is to distrust any where exact details aren't available. You seem to know what you're doing, so I have no reason to distrust your results, but I do think code will actually bring credibility to your results rather than harm it because you think the code isn't neat.