Code Review Should Start by Defining What a Change Must Preserve

·1 views

Software development has traditionally assumed humans will read and understand code, but AI-generated code output is making human reading speed a bottleneck. The article proposes judging changes by the properties they must preserve rather than by reading every implementation detail. It introduces "Laws" as stated properties, such as specification behavior, design rules, or compatibility requirements, that software must satisfy. Facts from the code are recorded as "Atoms" in a shared vocabulary within an "ArchMap," allowing AI to check whether the Laws hold. Because this vocabulary is independent of language or framework, the same Laws can apply across different implementations.

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)

Show HN project places employees inside S&P 500 market-cap bubbles

A Show HN post on Hacker News introduces a project that visualizes employees as bubbles positioned within S&P 500 market-cap comparisons. The project is hosted at bigwhalehunting.com and was shared on the Hacker News forum. The post received 8 points and no comments at the time of the source listing. The article text provided contains only the link and metadata, so the project's methodology and purpose beyond this description cannot be confirmed.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

Git changelog generator learns to handle non-main branch topologies

A developer built a deterministic changelog generator that diffs two commits and produces structured release notes without rewriting history. The first version assumed every team merges into main, which produced misleading output when projects used develop, master, release branches, or tags on feature branches. To fix this, the tool now accepts a branch parameter and resolves the merge-base automatically. When commits sit on divergent branches, it explicitly reports that instead of fabricating a linear history. The author's key takeaway is that changelog tools should treat git history as a DAG and compute changes via reachability set-difference rather than commit distance.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Apex Grid Shares Two-Stage GPU Preflight Check for Cron Agent Jobs

Apex Grid has described a two-stage preflight check it developed over several months to confirm GPU and serving-stack readiness before cron jobs run. The team argues that simply wrapping a job in a try/except block can hide failures caused by the GPU itself, such as another job monopolizing the card or an unresponsive kernel. The first stage queries a health endpoint, while the second runs a minimal inference request under a warmup timeout of roughly 3 to 10 seconds. The approach lets jobs be skipped cleanly when checks fail, which is useful when several cron jobs share a GPU pool, though it adds scheduling latency and requires specific endpoints. The company says it is exploring tuned lightweight warmup models and deeper Kubernetes integration.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Namely: a free tool that suggests descriptive file names using open-weight Gemma

Namely is a small web app that helps users stop leaving files with names like scan001.pdf or IMG_4432.jpg. A user uploads a single PDF, image, or text file, and the app returns three suggested names: a descriptive one, a short one, and a date-first one. Gemma 4, an open-weight model accessed through the Gemini API, generates the suggestions, and renaming happens in the browser so the original file is never sent back. The project is built with FastAPI, vanilla JavaScript, and Render hosting, and files are processed in memory and stripped of EXIF metadata such as GPS location. The developer also added safeguards against prompt injection and retry logic for intermittent free-tier model errors.

0 comments Read more at DEV Community