5 ms·
> This blog post is mostly written from memory, since I didn't keep around every version of the code being discussed. How do you track these optimization attem
by flakiness 2y ago
> This blog post is mostly written from memory, since I didn't keep around every version of the code being discussed.
How do you track these optimization attempts, given you don't commit many dead-end changes? CS major often doesn't teach how to experiment, which is a bummer as there supposed to be established ways to do it among other scientific disciplines. Maybe you can use something like Jupyter notebook? But what if the code is in, say, Rust and lives outside the Jupyter kernel.
- KeplerBoy 2y agoYou integrate the benchmarking process into the commit action (or vice versa) and simply commit everything that successfully completes benchmark. Might be an hour of additional effort at the beginning of the project, but will prove to be insightful at the end.
- flakiness 2y agoHow about changes that doesn't make number better? Just create a dead-end branch?