@xeophon made a "web-search <query>" script that i have my claude code prompted to call in place of its web search which runs o3 with its web tool enabled.. results are night and day.
@_xjdr@xeophon What does your deslopification workflow look like in cc? A stop hook that kicks off another headless cc to review the most recent changes? Running a slash command every so often to check for certain conventions? Manual review?
Since imo most llm problems are some careful data curation/collection/synthetic generation and gradient descent from a solution, “dataset centric thinking” opens a lot of doors
surprised people don’t think about data moats more (what models can we build with this data, what data do we need to collect to solve this problem, etc.) it’s always about retrofitting existing general solutions into specific problems
@darpinian Even just running benchmarks across diff quantization levels would be nice. I should be able to input my GPU and get a spat out chart of inference speed vs benchmark perf, with a highlighted answer like “in order to maintain >100 tok/s and x MMLU, you need to use 4 bit llama 70B”
@darpinian I’m aware of some huggingface spaces that can at least do “how much vram do I need” for diff models and quantization levels, but a single source of truth to point any newbie in the right direction would be awesome
@darpinian Scraping twitter for a hot papers and sentiment/analysis of opinions on the papers would be cool, though scraping twitter is now slightly more of a pain in the ass now that API is gone (iirc)