How a Late-Night Dev Session Built a Cross-Project Log System That Now Spans 426 Files

·2 views

A developer working with Claude Code created a session-tracking system during a brief early-morning session to solve the problem of continuity across multiple AI conversations. The system introduced a structured naming format, an index file, and an auto-closing script that logs session metadata including start time, status, and a UUID for resuming work. A third session the same day expanded the design, giving each session its own file with fixed sections for goals, decisions, and next steps, plus a script to list and query sessions at the start of each conversation. The system has since scaled to 426 session files across ten projects, with 165 created autonomously by agents running terminal tasks without the developer present. Core elements like the naming format and fixed section structure remain unchanged from that original night.

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)

CauterRule v0.3.0 Exposes Flaw in AI Rule Validation: Text Matching Masks True Accuracy

CauterRule, an open-source tool that converts repeated AI agent failures into reusable standing rules, released version 0.3.0 with findings from a field test covering 40 corpora and 4,768 trajectory runs across two cloud models. Developers discovered that the tool's replay gate, which decides whether an extracted rule gets promoted, relies on lexical text similarity rather than verifying whether a rule would actually change an agent's outcome. In one documented case, a correctly extracted git rule was demoted to 'inconclusive' because unrelated successful trajectories happened to share the token 'git' with the rule's trigger phrase. The team also found that extraction accuracy, measured by token-F1 against ground-truth rules, scored only around 0.50–0.58, not due to wrong outputs but because the model rephrases correct answers that a token comparator penalises. The release reframes the problem as two distinct challenges — rule extraction quality and replay verification validity — pointing to separate fixes needed for each.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer's SQL scanner missed 4 of 5 real CVEs, then a fix made things worse

A developer tested 'inlet', their open-source static SQL-injection scanner for Python codebases, against 15 real PyPI packages — five of which had documented, verified SQL-injection CVEs. The scanner failed to detect four of the five vulnerabilities because the vulnerable code routed through framework-level abstractions rather than the direct method names inlet was designed to recognize. A smaller bug was also uncovered: inlet misclassified safe calls in the Peewee ORM due to a method-name collision with standard database cursor calls. The developer built and shipped a fix that successfully reduced false positives in Peewee, but a follow-up check revealed the same rule silently dropped 94 genuine database call sites across other packages. Rather than ship a fix that improved one metric while degrading overall accuracy, the developer reverted the change and documented the 0-for-5 miss rate transparently in the project's evaluation file.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Enterprise AI Fails When Deployed on Broken Business Processes

Many enterprise AI projects begin by selecting a model rather than first examining the business process the technology is meant to improve. Poorly defined workflows — marked by unclear responsibilities, inconsistent data, and unwritten business rules — do not get fixed by AI; they get amplified. A human operator working with bad data may produce isolated errors, but an automated AI system can replicate those same errors across thousands of records at scale. The article argues that teams often spend weeks refining prompts while the root problem, flawed process design, remains unaddressed. Before choosing any AI model, organizations should clearly define process boundaries, data ownership, and measurable success criteria.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How One Developer Ran Proxmox and Docker on the Same Windows Machine

A developer discovered that Windows Hypervisor Platform and nested Proxmox virtualisation are mutually exclusive, forcing Docker Desktop to fail whenever Proxmox was active. After AI tools only suggested choosing one option, the developer devised their own fix: offloading the Docker daemon entirely to a dedicated Ubuntu VM running inside VMware. The Windows Docker CLI was then configured to communicate with that remote VM via SSH context, bypassing the hypervisor conflict altogether. The setup uses Docker Engine 29.8.0 on an Ubuntu 24.04 VM with 4 vCPUs and 8 GB RAM, while Docker Desktop on Windows is retained solely for its CLI. A noted side effect is that disabling the Windows hypervisor also silently breaks WSL2, despite status commands appearing normal.

0 comments Read more at DEV Community