Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-03-18 · source-backed
Speculative fiction imagining "Software Mechanics" — domain experts who fix AI-generated code's specification gaps. The central insight: ~60% of regenerated-software failures happen because external data sources change under a static spec, not because the AI wrote bad code. The mechanic's paradox: prevention is always cheaper, but humans reliably pay for crises instead. Near Zero Software
Each link below shares sources, entities, or timing with this story.
Scott Werner's speculative fiction piece (509 points, 313 comments on HN) argues AI-generated software shifts failures from buggy code to ambiguous natural-language specifications. A weather service recalibration cascades into a $25K crop-management failure because independent...
Everyone stuffing context into a coding agent has the same instinct: more surrounding code is more signal. Grab the neighboring files, pull in the commented examples, give the model a rich view of the module. arXiv 2609.09242 tested that on LiveCodeBench and the answer is wors...
Per the Google Cloud roundup, you can describe query intent in natural language instead of authoring SQL directly. It lowers the barrier between analysts and data. Useful, though I'd want to see how it handles the ambiguous 90% of real business questions before trusting it uns...
A developer published v100-skinny with hand-written NVFP4 W4A16 CUDA kernels plus chain-MTP speculative serving: four V100s at 219.1 ± 5.9 tok/s decode against a 5090 running NInfer at 214.7 ± 9.2, both 5/5 correct on AIME 2026 problem 1 across five seeds. (r/LocalLLaMA) The m...
Speculative decoding (a small draft model proposes tokens the target verifies in parallel) gives 2-5x latency wins, but only in memory-bound, low-batch regimes. At large batch sizes the GPU is already compute-bound, and the extra draft-and-verify work makes inference *slower*...
His September 3 essay pushes back on the idea that cheap tooling collapses enterprise software. His claim is that the value in SAP, Workday, Carta and Rippling was never the code, it was moving a workflow out of improvised spreadsheets and email into an institutionalized syste...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.