Engineering Insights

Is sunscreen the new margarine? (2019)

Comments

Age verification is just a precursor to automated attribution of speech

Article URL: https://nonogra.ph/age-verification-is-just-a-precursor-to-attribution-of-speech-06-29-2026 Comments URL: https://news.ycombinator.com/item?id=48714529 Points: 944 # Comments: 588

ISC Stormcast For Monday, June 29th, 2026 https://isc.sans.edu/podcastdetail/9986, (Mon, Jun 29th)

HackerRank open sourced its ATS. My resume scored 90/100. Oh wait 74. No – 88

Article URL: https://danunparsed.com/p/hackerrank-open-source-ats Comments URL: https://news.ycombinator.com/item?id=48713832 Points: 943 # Comments: 402

Sandboxes now expire based on last use

Vercel Sandbox snapshots now expire based on when they were last used, not when they were created. Active snapshots stay alive as long as workflows depend on them, while unused snapshots expire on their retention policy. Every time a snapshot is used, its expiration timer resets. This lets you set shorter retention windows without worrying that a snapshot will disappear between sessions, making it safer to build long-running workflows on top of Sandbox persistence. Learn more about Sandbox snaps

"Claude Code '400: no low surrogate in string' on every turn: repairing a permanently broken session transcript"

Originally published on hexisteme notes. A Claude Code session that returns API Error: 400 ... not valid JSON: no low surrogate in string on every turn is poisoned by a lone UTF-16 surrogate (a code point in U+D800–U+DFFF) baked into its on-disk transcript, and the fix is to close that session, strip only those lone surrogates from the offending line of the .jsonl file while leaving real emoji untouched, re-serialize that one line, and then claude --resume. The poison is already on disk and is p

Caching LLM responses is just content addressing

An LLM review costs money and a few seconds of latency. Reviewing the same diff twice should cost neither. CommitBrief caches every review, but the interesting part isn't that it caches — it's that the cache is content-addressed, so a hit is provably the same review, and there is no such thing as a stale one. Editing a single line of your rules file invalidates exactly the entries it should, and not one more, with zero invalidation logic anywhere in the code. TL;DR The cache key is a SHA-256 of

Your AI isn’t underperforming. Your data foundation is.

New research shows Australian businesses are blowing AI budgets on tokenmaxxing instead of fixing their underlying data foundations. Discover why data quality, not the model, determines your true AI ROI for the new financial year.