Related reading
Pruning LLMs Like a Physicist: Block Removal as an Ising Optimization Problem
The authors cast transformer block removal as a constrained binary optimization problem equivalent to an Ising glass, using a Hessian‑derived energy as a proxy for downstream quality. Solving the resulting QUBO with classical or quantum‑inspired solvers yields up to 23 MMLU points improvement over prior block‑removal baselines at 50 % depth compression.
Hugging Facehuggingface.co8 minArticle: Architecting Secure and Scalable Facial Verification Systems
A real‑world post‑mortem of a high‑volume face verification service that moved from a naïve synchronous API to an async, layered pipeline (edge validation, preprocessing, decoupled detection/verification, decision engine) to achieve 8.5k rpm, p99 < 1.8 s, 30 % cost savings, and strict privacy controls.
InfoQinfoq.com15 minArticle: Your Next DSL Author Is a Language Model
Typed Domain Grounding (TDG) embeds a DSL inside a mainstream language the LLM already knows (e.g., Kotlin) and uses the host compiler as an oracle. The author describes five building blocks—embedding, choosing a host language with high training‑data frequency, compiler‑driven type safety, a generate‑compile‑repair loop, and an on‑demand teaching tool—and shows measured results from kUML, a Kotli…
InfoQinfoq.com18 minFive models pass the easy code reviews. Then the diffs get hard.
A hands‑on benchmark of five LLM code‑review models (Claude Opus 5, GPT 5‑6 Sol, Grok 4.6, Kimi 3, GLM 5.3, Qwen 3.8 Max, DeepSeek v4 Pro) shows that all models ace tiny 15‑line diffs but diverge sharply on 100‑300‑line, cross‑file changes. The author built a deterministic harness (single HTTP call, fixed system prompt, JSON output) and measured detection rate, false‑positives, latency, token usa…
Bjørn Johansenbjornjohansen.com16 minWhy I'm still bearish on LLMs after Navier-Stokes
The author argues that despite headline successes (e.g., Navier‑Stokes proof, security exploits), current frontier LLMs still require heavy human oversight and rigorous specifications that are costly to produce. Reward‑hacking, narrow generalization, and the need for domain‑expert spec writing limit autonomous deployment to only a few niche domains (high‑failure‑cost work, tightly defined tasks,…
