0 views collected around this technical thread.
The author recounts a late‑night incident where a newly launched marketing tool malfunctioned due to a boolean logic error in Java code, describes the chaotic debugging process, presents the faulty and corrected implementations, and confirms the logical equivalence of the final solution.
This article examines the practical challenges of using large language models in software development, including handling long contexts, cross‑file editing, bug‑fixing evaluation methods, and presents benchmark results from SWE‑Bench and its Lite subset to assess model capabilities.
This article recounts three production‑level pagination bugs encountered in a payment system, explains why they occurred—ranging from naive batch processing to MySQL's nondeterministic LIMIT behavior—and shows how proper pagination, ThreadLocal cleanup, and deterministic ordering resolve the issues.
The report analyzes SonarQube‑detected defects in Projects A and B, classifying them by type and severity, revealing that code smells dominate while null‑pointer bugs are unexpectedly frequent, and discusses why some defects are quickly fixed versus others remaining unresolved, emphasizing early detection, design rigor, and robust testing.
Researchers from Germany and the UK evaluated ChatGPT and three other AI models on the QuixBugs benchmark, finding that ChatGPT correctly fixed 31 of 40 bugs—outperforming CodeX, CoCoNut, and Standard APR—and sparked mixed reactions about its impact on software engineering and OpenAI’s broader strategies.
Based on Google Project Zero data from 2019 to 2021, Linux leads with an average bug‑fix time of 15 days, while Oracle shows the most delay, and Chrome and iOS consistently rank among the fastest in patching security vulnerabilities.
The article reviews three common boundary‑value bugs encountered during software testing, explains why they occur, shows the original C code that triggers each issue, and provides concise corrections to prevent off‑by‑one errors and buffer overflows.
To keep product development sustainable, prioritize user‑reported bugs first, then self‑discovered bugs, followed by user‑requested features and finally internal ideas, using continuous ranking based on impact, difficulty, and supporter count while actively listening to users and fixing problems before adding new functionality.
This article reviews three typical boundary‑value bugs encountered during software testing—incorrect memory size checks, off‑by‑one retry counters, and misplaced increment operations—explaining their causes, showing original C code, and providing concise corrective solutions.
After a rushed fix for a division‑by‑zero bug caused incorrect results, the team learns to validate data at its source, adopt proper validation frameworks, and step back to understand underlying requirements, emphasizing that thoughtful design outweighs quick code patches.