Tag: #debugging
Writing on GPUs, LLMs, MLOps, Kubernetes — and mindset · 22 posts
22 posts are tagged #debugging; the most recent was published on 2026-09-10.
Often tagged together: #2026-03 7 #devops 5 #practical-guide 5 #ai 4 #career 4
Most read in the last 90 days:
VBR MP3 breaks transcript clicks — CBR vs VBR, measured
Clicking a transcript line jumped to the wrong place. The cause was the audio container, not the timestamps. Why the Xing TOC in a VBR file drifts up to 0.9 seconds, why CBR stays within 0.04, and what 96 real episodes s
2026-09-10 · 6 min read #audio#mp3#ffmpeg#web#debuggingAI for Everyone, Part 3 — Loss of 0.0017, Accuracy of 7.5%: The Culprit Was One Padding Slot
We built a VQA model — one that answers questions about an image — with 1.48 million parameters. Training loss fell to 0.0017 while accuracy sat at 7.5%, worse than guessing. The cause was not the model but a single line
2026-08-21 · 8 min read #ai#vqa#multimodal#debugging#pytorchWhy Debugging Resists Replacement — The Craft of Elimination
Debugging runs in the opposite direction from writing code. Writing produces one possible thing; debugging erases possible causes until one is left. This piece covers why debugging sits on the expensive-to-verify side, h
2026-08-15 · 6 min read #career#skills#debugging#craft#troubleshootingKorean Dev Blog Curation 2 — Incident Retrospectives and Troubleshooting, 12 Posts I Opened and Checked
The genre Korean developers write best is the incident retrospective. Twelve posts: p6spy silently defeating read/write datasource routing, why an HTTP timeout does not cover DNS resolution, a TCP half-close disguised as
2026-08-12 · 12 min read #curation#큐레이션#troubleshooting#postmortem#incidentThe FDE Incident Diagnosis Playbook — Six Steps from Access to Report
The decisive difference between an incident on your own service and one at a customer site is that the latter starts from knowing nothing. That is why a Forward Deployed Engineer (FDE) needs a fixed order before needing
2026-08-12 · 6 min read #career#fde#forward-deployed-engineer#incident-response#debuggingThe goroutineleak Profile in Go 1.26 — Catching Goroutine Leaks with GC Marking
Go 1.26 (released February 10, 2026) added a goroutineleak profile to runtime/pprof as an experimental feature. The idea is to recycle the GC's marking phase — mark using only runnable goroutines as roots, then report as
2026-07-16 · 17 min read #go#goroutine#garbage-collection#profiling#debuggingThe eBPF Verifier Only Tells You Where It Stopped — Measuring the Diagnostic Gap Across 235 Reproduced Rejections
Anyone who has used eBPF has lived this: the verifier rejects your program, and the error message points at a line that looks perfectly innocent. A paper published in July 2026 is the first to put a number on that frustr
2026-07-16 · 18 min read #ebpf#linux#kernel#debugging#developer-experienceWhen Code Generation Gets Cheap, Which Skills Go Up in Value — What Depreciates and What Appreciates
When code generation becomes cheap and abundant, value does not vanish — it moves to whatever is still a bottleneck. Right now that bottleneck is verification, judgment, and integration. Building on Jason Wei's asymmetry
2026-07-12 · 14 min read #career#software-engineering#ai#skills#code-reviewDebugging Like a Scientist: Hypothesis-Driven Debugging
Instead of staring at code and changing things at random, debug like a scientist: form a hypothesis, make a prediction, and test it. Binary-search the problem space, build a minimal reproducible example, hunt the culprit
2026-07-03 · 14 min read #debugging#engineering#productivity#fundamentalsReading Logs and Stack Traces Like a Detective
A stack trace is a crime scene; logs are witness statements. How to read a stack trace top to bottom (the top is where it blew up, the bottom is the origin), follow the "caused by" chain, use structured/JSON logging, cor
2026-06-28 · 13 min read #logging#debugging#stack-trace#observabilityHow to Be Good at Programming — Principles, Habits, and Depth
A builder essay that defines what being good at programming actually means, then works through fundamentals and debugging, abstraction and simplicity, readable code, testing, deliberate practice, reading code, and the sk
2026-06-16 · 17 min read #programming#craft#deliberate-practice#debugging#code-qualitySoftware Debugging Mastery 2026 - GDB / LLDB / rr / Pernosco / pdb / Chrome DevTools / Bun inspect / DAP Deep Dive ♪ Listenable
A May 2026 survey of the software debugging stack and the mindset behind it. Reverse and time-travel debugging with GDB 15, LLDB 19, rr, and Pernosco; Chrome DevTools 2025 with AI assistance and MCP; built-in inspectors
2026-05-16 · 25 min read #debugging#gdb#lldb#rr#pernoscoSoftware Debugging Tools 2026 Deep Dive — gdb, lldb, rr, Pernosco, Replay.io, ASan, Valgrind, eBPF, perf, Time-Travel Debugging ♪ Listenable
A full map of the 2026 debugging landscape in one read. From the undefeated reign of printf to interactive debugging with gdb/lldb, time-travel and omniscient debugging via rr/Pernosco/Replay.io, the ASan-vs-Valgrind tra
2026-05-16 · 25 min read #debugging#gdb#lldb#rr#pernoscoSystematic Debugging — Finding Bugs by Reasoning, Not Guessing ♪ Listenable
Most debugging is undisciplined guessing. The core loop — reproduce, isolate, hypothesize, test, fix, verify — plus git bisect and binary search, how to read stack traces properly, the hard bug classes like heisenbugs an
2026-05-14 · 23 min read #debugging#methodology#engineering-craft#git-bisect#observabilityVMI Status, Metrics, Guest Agent, Debugging: How KubeVirt Exposes Internal State
Describes how KubeVirt collects and exposes VM internal state through VMI status, guest agent, domain stats, Prometheus metrics, and virt-handler API, based on code analysis.
2026-03-20 · 6 min read #architecture#kubevirt#observability#metrics#guest-agentDeep Learning Debugging Complete Guide: From Diagnosing Training Failures to Performance Optimization
A complete guide to systematically diagnosing and resolving deep learning training failures. Covers Loss NaN, vanishing/exploding gradients, overfitting, slow convergence, and out-of-memory errors with real-world code ex
2026-03-17 · 19 min read #deep-learning#debugging#pytorch#training#optimizationIDE Debugging Playbook: VS Code, IntelliJ IDEA, and PyCharm
Part 3 of the debugging series. A practical, copy-paste-friendly guide with reproducible steps, breakpoint strategy, profiling checkpoints, and team-level checklists.
2026-03-07 · 2 min read #devops#debugging#practical-guide#2026-03Remote Debugging Guide: SSH Tunnel + VS Code/IntelliJ/PyCharm
Part 5 of the debugging series. A practical, copy-paste-friendly guide with reproducible steps, breakpoint strategy, profiling checkpoints, and team-level checklists.
2026-03-07 · 2 min read #devops#debugging#practical-guide#2026-03Debugging Casebook: Language × Framework Failure Patterns
Part 4 of the debugging series. A practical, copy-paste-friendly guide with reproducible steps, breakpoint strategy, profiling checkpoints, and team-level checklists.
2026-03-07 · 2 min read #devops#debugging#practical-guide#2026-03Debugging by Language: Python, JavaScript/TypeScript, Go, and Java Practical Guide
Part 1 of the debugging series. A practical, copy-paste-friendly guide with reproducible steps, breakpoint strategy, profiling checkpoints, and team-level checklists.
2026-03-07 · 2 min read #devops#debugging#practical-guide#2026-03