<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Quant Research on WM's Blog</title><link>https://wins-m.github.io/302/en/tags/quant-research/</link><description>Recent content in Quant Research on WM's Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 20 Aug 2026 12:00:00 +0800</lastBuildDate><atom:link href="https://wins-m.github.io/302/en/tags/quant-research/index.xml" rel="self" type="application/rss+xml"/><item><title>Once Experiment Cost Approaches Zero, What Does Research Itself Become?</title><link>https://wins-m.github.io/302/en/posts/2026/zero-cost-experiments/</link><pubDate>Thu, 20 Aug 2026 12:00:00 +0800</pubDate><guid>https://wins-m.github.io/302/en/posts/2026/zero-cost-experiments/</guid><description>&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;30-second version:&lt;/strong&gt; What AI really lowers isn&amp;rsquo;t the cost of writing code — it&amp;rsquo;s the &lt;strong&gt;search cost&lt;/strong&gt; across the entire hypothesis space. An idea that used to have a 20% success rate and take two days to test wasn&amp;rsquo;t worth trying before; now it is.&#10;So the bottleneck moves from execution to selection: when you can run two hundred experiments a day, the hard part is &lt;strong&gt;which two are worth looking at&lt;/strong&gt;.&#10;And alpha discovery has gotten cheap — alpha validation hasn&amp;rsquo;t. As the search space grows, multiple testing, overfitting, and selection bias all get worse; you can always fish a pretty equity curve out of pure noise.&#10;So the researcher&amp;rsquo;s job shifts from &amp;ldquo;finding one good result&amp;rdquo; to &amp;ldquo;ranking a pile of results by strength of evidence.&amp;rdquo; What&amp;rsquo;s scarce is no longer the ability to search, but the &lt;strong&gt;prior knowledge of where to search&lt;/strong&gt;, and the discipline to actually kill a signal.&lt;/p&gt;</description></item><item><title>When Writing Code Is No Longer the Bottleneck in Quant Research</title><link>https://wins-m.github.io/302/en/posts/2026/quant-research-bottleneck/</link><pubDate>Thu, 20 Aug 2026 00:00:00 +0800</pubDate><guid>https://wins-m.github.io/302/en/posts/2026/quant-research-bottleneck/</guid><description>&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;30-second version:&lt;/strong&gt; AI agents can now read code, run experiments, and fix bugs on their own — writing code is no longer the bottleneck in quant research.&#10;So what&amp;rsquo;s scarce is no longer &amp;ldquo;how many experiments can I run,&amp;rdquo; but &lt;strong&gt;what&amp;rsquo;s worth trying&lt;/strong&gt;, and &lt;strong&gt;what results are worth believing&lt;/strong&gt;.&#10;The researcher&amp;rsquo;s role isn&amp;rsquo;t just &amp;ldquo;the one who asks questions&amp;rdquo; either — asking is just as cheap now; what&amp;rsquo;s genuinely hard is designing experiments that can distinguish between competing explanations.&#10;Once execution gets cheap, you&amp;rsquo;re not facing an empty ocean — you&amp;rsquo;re facing an ocean that suddenly has a few hundred extra boats in it. The problem shifts from &amp;ldquo;how do I find something&amp;rdquo; to &amp;ldquo;how do I know what I found isn&amp;rsquo;t just glass shards.&amp;rdquo;&lt;/p&gt;</description></item></channel></rss>