korrents

On the map

Tap a claim on the ring to put it at the centre.

← Retries should be logged even when they succeed, otherwise they look like unexplained performance regressions.

17 connected korrents · 10 moments from 18 Dec 2023 to 11 Oct 2026.

Everything filed under software performance software performance Everything filed under design design Everything filed under humility humility Everything filed under patience patience Everything filed under software quality software quality Everything filed under AI agents AI agents Everything filed under cybersecurity cybersecurity Everything filed under developer tools developer tools Same subjectSame subjectSame subjectSame subjectSame subjectSame subjectSame subjectSame subjectSame subjectSame subjectSame subjectSame subjectSame subjectSame subjectSame subjectSame subjectSame subject Read this korrent: Retries should be logged even when they succeed, otherwise they look like unexplained performance regressions. Retries should be logged even when theysucceed, otherwise they look likeunexplained performance regressions. Last stated 2 years ago 9 Dec 2024 HS Hynek Schlawack — holds since 2024-12-09 — tap for who they are Same subject: Because the cause of a failure is unknown, retries should start with a short backoff and increase it exponentially. — tap to centre the map on it Because the cause of a failure isunknown, retries should start with ashort backoff and increase itexponentially. Last stated 2 years ago 9 Dec 2024 HS Hynek Schlawack — holds since 2024-12-09 — tap for who they are Same subject: Retries need random jitter, because identical backoffs still make all clients retry at the same time. — tap to centre the map on it Retries need random jitter, becauseidentical backoffs still make allclients retry at the same time. Last stated 2 years ago 9 Dec 2024 HS Hynek Schlawack — holds since 2024-12-09 — tap for who they are Same subject: Retries must stop eventually because not everything recovers within a useful time frame. — tap to centre the map on it Retries must stop eventually becausenot everything recovers within auseful time frame. Last stated 2 years ago 9 Dec 2024 HS Hynek Schlawack — holds since 2024-12-09 — tap for who they are Same subject: When narrowing a bug reproduction case, it should still be possible to obtain a passing result with the new case, not just a failing one. — tap to centre the map on it When narrowing a bug reproductioncase, it should still be possible toobtain a passing result with the newcase, not just a failing one. Last stated a year ago 21 Oct 2025 DA Dan Abramov — holds since 2025-10-21 — tap for who they are Same subject: Long-running agent tasks need a durable workflow rather than a job queue, so a retry after a failure resumes where it stopped. — tap to centre the map on it Long-running agent tasks need adurable workflow rather than a jobqueue, so a retry after a failureresumes where it stopped. Last stated a month ago 11 Oct 2026 LR Lee Robinson — holds since 2026-10-11 — tap for who they are Same subject: Retry parameters can be tuned as long as the backoff is exponential and has an upper bound. — tap to centre the map on it Retry parameters can be tuned aslong as the backoff is exponentialand has an upper bound. Last stated 2 years ago 9 Dec 2024 HS Hynek Schlawack — holds since 2024-12-09 — tap for who they are Same subject: Services retrying immediately after a shared failure can amount to a distributed denial of service attack against yourself. — tap to centre the map on it Services retrying immediately aftera shared failure can amount to adistributed denial of service attackagainst yourself. Last stated 2 years ago 9 Dec 2024 HS Hynek Schlawack — holds since 2024-12-09 — tap for who they are Same subject: The steady stream of "we had to rewrite the whole thing because it was too slow" engineering blog posts is the proof that deferring performance to hotspot optimization does not work. — tap to centre the map on it The steady stream of "we had torewrite the whole thing because itwas too slow" engineering blog postsis the proof that deferringperformance to hotspot optimizationdoes not work. Last stated 3 months ago 26 Aug 2026 CM Casey Muratori — holds since 2026-08-26 — tap for who they are Same subject: "Is the page loaded?" was never a real question, and web performance only became measurable once it was broken into the distinct moments a user actually notices. — tap to centre the map on it "Is the page loaded?" was never areal question, and web performanceonly became measurable once it wasbroken into the distinct moments auser actually notices. Last stated 3 months ago 19 Aug 2026 AO Addy Osmani — holds since 2026-08-19 — tap for who they are Same subject: "Optimize it later" would be safe advice only if every engineer already knew how to avoid the architectural mistakes that no later optimization can remove. — tap to centre the map on it "Optimize it later" would be safeadvice only if every engineeralready knew how to avoid thearchitectural mistakes that no lateroptimization can remove. Last stated 3 months ago 26 Aug 2026 CM Casey Muratori — holds since 2026-08-26 — tap for who they are Same subject: A 300-millisecond response budget is not an achievement but an admission: 300 milliseconds is an eternity in computing, and a product pitching it shows how far the bar has fallen. — tap to centre the map on it A 300-millisecond response budget isnot an achievement but an admission:300 milliseconds is an eternity incomputing, and a product pitching itshows how far the bar has fallen. Last stated 3 months ago 26 Aug 2026 CM Casey Muratori — holds since 2026-08-26 — tap for who they are Same subject: A profiler measures time already spent in an operation, not how much time would be saved by optimizing it. — tap to centre the map on it A profiler measures time alreadyspent in an operation, not how muchtime would be saved by optimizingit. Last stated 3 years ago 18 Dec 2023 NE Nelson Elhage — holds since 2023-12-18 — tap for who they are Same subject: For GPU performance, flops do not matter so much as the whole memory access pattern does, and torch.compile cannot find every optimization. — tap to centre the map on it For GPU performance, flops do notmatter so much as the whole memoryaccess pattern does, andtorch.compile cannot find everyoptimization. Last stated 2 years ago 9 Jun 2024 AK Andrej Karpathy — holds since 2024-06-09 — tap for who they are Same subject: Monitoring tools that do periodic work can themselves cause the latency outliers they were installed to diagnose. — tap to centre the map on it Monitoring tools that do periodicwork can themselves cause thelatency outliers they were installedto diagnose. Last stated a year ago 3 Aug 2025 BG Brendan Gregg — holds since 2025-08-03 — tap for who they are Same subject: Compiler mechanisms that force a required optimization to occur, rather than relying on incidental compiler behavior, are a more robust way to write performance-sensitive code. — tap to centre the map on it Compiler mechanisms that force arequired optimization to occur,rather than relying on incidentalcompiler behavior, are a more robustway to write performance-sensitivecode. Last stated 2 years ago 9 Mar 2025 NE Nelson Elhage — holds since 2025-03-09 — tap for who they are Same subject: What clean-code polymorphism really costs you is not the virtual call but the optimizations the compiler can no longer perform once it cannot see what runs. — tap to centre the map on it What clean-code polymorphism reallycosts you is not the virtual callbut the optimizations the compilercan no longer perform once it cannotsee what runs. Last stated 3 months ago 26 Aug 2026 CM Casey Muratori — holds since 2026-08-26 — tap for who they are Same subject: A compiler that also serves an IDE has to be lazy and deferred throughout — a different way of building compilers from the one the textbooks teach. — tap to centre the map on it A compiler that also serves an IDEhas to be lazy and deferredthroughout — a different way ofbuilding compilers from the one thetextbooks teach. Last stated 6 months ago 13 May 2026 AH Anders Hejlsberg — holds since 2026-05-13 — tap for who they are
same subject or similar wordinga cloud: claims about one subject, named for itbar: when it was last stated, on a scale from 2015 to today — full is todaya face: someone who holds the claim — tap it for who they are

At the centre Retries should be logged even when they succeed, otherwise they look like unexplained performance regressions. Last stated 9 Dec 2024 · 2 years ago Holds Hynek Schlawack Read this korrent →