Scheduling a factory, routing a fleet, pricing airline seats, allocating scarce capacity: these are not “write me a Python script” problems with nicer stationery. In real operations research, the useful answer is not merely a correct mathematical model. It is a method that stays feasible, keeps solution quality high, and finishes before the business context has expired. ...
No Easy A: Why AI Training Needs Hard-Case Routing AI teams like to say they are “improving the model.” Very noble. Also conveniently vague. In practice, “improvement” usually means one of three things: collect more data, buy a larger model, or run another round of fine-tuning and hope the loss curve behaves like a polite employee. The two papers in this cluster suggest a less glamorous, more useful idea: the scarce resource is not only data or parameters. It is learning pressure. ...
GPU memory is the part of AI strategy that does not care about adjectives. A team can say it is building a domain LLM, a private copilot, a long-context research assistant, or a fine-tuned enterprise model. The budget spreadsheet eventually asks a colder question: what actually fits on the available hardware? Model weights need memory. Gradients need memory. Activations need memory. Checkpoints need memory. And the optimizer — the quiet machinery that decides how parameters move during training — can require multiple additional copies of the model itself. ...
A developer asks an LLM to “write a better algorithm.” The LLM obliges. It writes code. The code runs, perhaps after a few rounds of apologetic debugging. The result is slightly better than the baseline, or at least sufficiently mysterious to be called “novel.” Everyone nods politely. Another benchmark table is born. ...
A warehouse manager does not ask for “a constraint optimization problem.” She asks whether tomorrow’s orders can be shipped without overtime. A university administrator does not request “a mixed-integer formulation.” He asks whether lectures can be scheduled without room conflicts. A retail planner does not want “a MiniZinc model.” She wants to know which stores should receive scarce inventory before the promotion starts. ...
Benchmarks are supposed to settle arguments. In practice, they often create better-looking arguments. A logistics optimizer claims it balances distance, delivery time, fuel cost, and risk. A robot planner claims it can trade off speed against safety. A routing engine claims it returns not one answer, but a frontier of reasonable alternatives. Fine. Then comes the awkward question: tested on what? ...
Search is where many AI systems become embarrassingly human. They try one move. It fails. They try a nearby move. It fails. Then, with the serene confidence of a spreadsheet macro wearing a lab coat, they try the first move again. That is the real problem behind many “autonomous research” demonstrations. The issue is not always that the model cannot propose useful ideas. It is that the loop around the model is fixed: propose a change, run an experiment, evaluate the result, keep or discard. Once this loop gets stuck, the system often has no way to ask the more important question: is my search process itself badly designed? ...
A print farm does not usually fail because nobody knows how to press “start.” It fails in smaller, duller, more expensive ways. One plate carries too few parts. Another job needs manual rearrangement. A failed object ruins the economics of a batch. The slicer accepts a layout that looks reasonable, until sequential printing reminds everyone that the print head is not a ghost and cannot pass through already printed objects. Reality, inconveniently, still has geometry. ...
Energy is the easy variable; deployment is the harder one Energy. That is usually where the sustainable AI conversation begins, and not without reason. AI infrastructure consumes electricity, advanced models require expensive compute, and the supply chain behind chips, data centers, cooling systems, and cloud capacity is not exactly made of recycled poetry. ...
Plans fail in painfully ordinary ways. A warehouse robot cannot both reserve the last pallet slot and keep the aisle clear. A field-service schedule cannot satisfy every customer window after one technician calls in sick. A compliance workflow cannot approve a transaction before the missing document exists, no matter how passionately the dashboard insists on “urgent priority.” ...