Click any tag below to further narrow down your results
Links
Randy Au argues that LLMs can take over tedious coding work in data analysis, but exploratory data analysis still needs a human who understands the data's context and intent. He says current models make poor analytical decisions and that the act of poking at data is how analysts sharpen their hypotheses.
- Exploratory analysis depends on intent: the same numbers look "correct" or "weird" depending on what you plan to do, and an LLM has no access to that purpose unless you spell out a huge amount of business context.
- Coding agents lack a feedback signal for analytical quality, so they confidently run off on flawed approaches. Au says he had to micromanage them to the minute detail, and the promised analysis often didn't match what was delivered.
- Hypothesis generation happens through hands-on iteration with the data. Offloading that work skips the process where questions get refined and interesting correlations get noticed.
@JayaGup10 on X
The post argues that the all-purpose LLM is splitting apart: judgment, ranking, search, and verification are getting priced and built as separate cheap layers, with frontier models reserved for the hardest work. It introduces Jev from TypeSafe as an example of packaging one decision step as its own model call.
- Agents make hundreds or thousands of model calls per task, so small per-step cost and latency differences add up to the whole product's economics.
- A "decoder tax" is paid when a model generates a full sentence just so the app can turn it back into a yes/no, urgent/not-urgent, or which-tool decision.
- Cheap enough judgment lets software check 100% of agent actions and customer interactions instead of sampling 1%, which opens product categories that aren't economical today.