Using AI as a Code Reviewer, Not a Code Writer, Catches More Bugs

·10 views

A software developer shared how shifting from AI-generated code to AI-assisted code review changed their development workflow. Instead of prompting AI to write code from scratch, they wrote the code themselves and then asked AI to review it as a senior engineer would. The AI surfaced edge cases and potential bugs — such as empty inputs, failed API responses, and missing values — that had been overlooked during manual testing. However, the developer notes that AI reviews are not always accurate and can sometimes flag non-issues or suggest overcomplicated fixes. The key takeaway is that AI works best as an additional perspective in the review process, with the developer retaining final judgment on what actually needs to change.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

SoundScript Library Lets .NET Apps Generate Audio Dynamically from App State

A .NET library called SoundScript, targeting .NET 10, enables developers to generate audio procedurally from application state rather than relying on static WAV file libraries. Instead of maintaining separate audio files for every event variation, developers define musical rules — including tempo, dynamics, and motifs — that map directly to runtime conditions. For example, a warning sound's intensity can automatically scale with a severity level, or a game's background tempo can increase as a player advances through levels. The library compiles a simple text-based script describing musical intent and renders it into a WAV file on the fly. This approach reduces asset management overhead in games and interactive applications where sound needs to vary based on changing runtime data.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Silent JS Bugs Skewed Months of Analytics on a Live Product Search Site

A developer running OneFindMe, a multilingual AliExpress product search engine, discovered a cluster of long-standing JavaScript bugs only after installing a session-recording tool — despite all automated checks showing green. A flawed HTML-entity escaping method in inline click handlers caused syntax errors for product titles containing apostrophes, silently breaking favourite, share, and analytics tracking on roughly a third of every results page. Because the underlying product links remained intact, no sales were directly lost, but click-through rate data collected over months was systematically undercounted, corrupting product decisions made on that data. A second bug referenced a renamed CSS class that no longer existed, rendering two buttons completely inert, a fact only made visible when session recordings showed a user clicking the same dead button five times in 26 seconds before abandoning the session. The incident highlights that passing automated checks does not confirm a working user experience, and that client-side errors which leave no server-side trace can only be reliably caught through direct page observation.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

SoundScript Library Lets .NET Apps Generate Audio from JSON Data

A .NET package called SoundScript enables developers to convert structured JSON data into WAV or MIDI audio files without building a dedicated audio engine. The library, version 13.0.0 targeting .NET 10, works by letting the application map its own JSON schema to SoundScript source code, which then handles compilation and rendering. Developers can link business logic variables — such as alert severity or application state — to musical parameters like dynamics and note sequences. The tool maintains a clear separation between application data and audio rendering, keeping business rules within the application layer. SoundScript is available via NuGet and is positioned for use cases where audio output needs to respond dynamically to changing application state.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Recover Vanished Chat History in Google Antigravity IDE

Developers using Google Antigravity IDE have reported chat histories disappearing from the sidebar after updates, reinstalls, cache clears, or periods of inactivity. The data is not actually deleted but enters a dormant state on disk, as the IDE avoids loading hundreds of conversation trajectories into frontend memory simultaneously. Conversations are stored in SQLite database files under ~/.gemini/antigravity-ide/conversations/ and can be reactivated by triggering a sync event through the IDE's internal Language Server daemon. One discovered workaround involves submitting a comment via an open artifact's Review menu, which wakes the dormant conversation and restores it to the sidebar instantly. For cases without an open artifact, the article outlines two open-source tools — a VS Code extension and a standalone Python script — designed to restore conversations on demand.

0 comments Read more at DEV Community