J.G.Montoya.Hodl
· 2d
When I'm optimizing some part of a codebase, I end up in the same loop. Try a thing. Benchmark. Keep what helps. Discard what doesn't. Repeat until the result is good enough, or until I get bored.
It...
A few things worth surfacing from v0.11.0.
There's a walkthrough for the optimization loop end-to-end: github.com/jgmontoya/shaka/blob/master/docs/autoresearch-walkthrough.md `shaka optimize` and `shaka autoresearch` are aliases. Same command tree. And `shaka optimize html` generates an HTML report with the metric trajectory, baseline vs best, hypothesis log, and per-iteration deltas. Safe to run mid-experiment.
Two more skills shipped this version too. `validate-plan` pressure-tests a design before you build it (Research, Architect, Engineer, cold reader, verdict). `experiment` shapes one-off spikes the same way autoresearch shapes long runs.