Machine Learning

A practical comparison of large language models and classical machine learning, with guidance on when each approach fits a business problem.

TL;DR for operators A development team wants to identify energy-expensive Java methods early, without repeatedly profiling every code change on controlled hardware. Source-level features such as complexity, calls, loops, and control flow appear to offer a cheap signal because they can be extracted before the software runs. In this study, those features were almost useless without runtime evidence. When the researchers reran the same Random Forest prediction setup after removing execution time, predictive $R^2$ fell from 0.454 to 0.005. Code features that look operationally meaningful therefore provided almost no useful prediction until a timing signal was added. ...

TL;DR for operators The classifiers have been tested, the predictions are fixed, and the evaluation meeting expects the metric table to reveal an obvious winner. Yet on the yeast multilabel dataset, one way of averaging F1 ranked BR-kNN first and BR-SVM last, while another produced the exact opposite ordering. Nothing about the models or predictions changed; only the unit given equal influence changed. ...

TL;DR for operators A clustering score is not a neutral verdict. It is a policy for deciding which mistakes count. Pasi Fränti’s review of external clustering measures separates that policy into three choices: how predicted clusters are matched to reference clusters, how similarity is scored, and how results are normalized.1 Those choices determine whether the metric rewards getting many individual records right, getting each cluster right regardless of size, or locating the correct cluster structure. ...

TL;DR for operators AI deployment is no longer mainly a question of whether a model can produce something plausible. That problem has been solved often enough to become boring, which is usually when businesses start wasting money at scale. The live problem is control. Which model should be trusted on this workload? When should a system query another model, pay more, or stop? When an LLM produces an analytical “insight”, is it finding the pattern you care about, or merely discovering an aggregate confound wearing a nice blazer? ...

Everyone wants the grand AI replacement story. The model eats the stack, digests the workflow, and emits profit. Very tidy. Also, usually nonsense. The more interesting pattern emerging in applied AI is smaller, less theatrical, and considerably more useful: the model is not the system. It is an intervention inside the system. It edits one field. It predicts one missing signal. It routes one candidate generator. It enters through a side door, preferably wearing a badge. ...

Errors are expensive. That is the boring sentence underneath most quantum computing roadmaps. A physical qubit is noisy, so engineers encode one logical qubit into many physical qubits. If the target computation is large enough, the redundancy becomes enormous. Then the spreadsheet starts doing what spreadsheets do best: quietly turning physics into capital expenditure. ...

Explanation is not free. That sounds obvious until one watches an AI system in production. A model predicts. A user asks why. The platform dutifully runs SHAP, LIME, saliency maps, or some carefully branded interpretability module, then presents a ranked list of “important” features with the solemn confidence of a consultant who has just discovered a bar chart. ...

Confidence is cheap. Calibration is expensive. That is the uncomfortable lesson behind a new arXiv paper on earthquake source inversion, a domain that sounds safely remote until one notices the pattern: a complex physical simulator, uncertain model inputs, high-dimensional observations, and a decision-maker who wants a probability distribution rather than a shrug.1 Replace “earthquake waveform” with “financial stress scenario,” “robot sensor stream,” “industrial digital twin,” or “clinical simulator,” and the problem becomes less geological and more familiar. ...

Inventory is the moment when a forecast stops being a spreadsheet exercise and starts costing money. A demand model can look elegant in validation. It can shave RMSE by a few decimals, win a leaderboard, and make the data science team briefly feel like civilization has advanced. Then the warehouse over-orders slow-moving stock, the store misses fast-moving items, and the finance team discovers that “better accuracy” is not the same thing as better cash flow. ...