SShortSingh.

Programming

0
ProgrammingDEV Community ·

Golden Datasets Rot Silently, Making AI Agent Evals Unreliable Over Time

AI evaluation frameworks rely on 'golden datasets' — fixed sets of expected outputs used to grade agent behavior — but these benchmarks quietly become outdated as APIs change, correct answers evolve, and policies are updated. Because test suites only check whether outputs match stored fixtures rather than real-world accuracy, a consistently green dashboard can mask a deeply flawed evaluation oracle. Engineers at senior levels repeatedly discover this failure mode late, long after the golden dataset has drifted from reality. A tiered evidence framework categorizes eval signals by independence: deterministic checks like valid JSON or file existence rarely rot, statistical baselines degrade slowly, while model-as-judge scores and hand-frozen golden strings decay fastest and most silently. Experts recommend treating only the first two tiers as real-time gates and restricting model-based judgment to offline evaluation to avoid circular, substrate-shared assessments.

0
ProgrammingHacker News ·

Study finds melatonin may impair morning cognitive function in young adults

A study published in the journal Sleep examined the effects of melatonin on cognitive performance in healthy young adults. Researchers found that melatonin use was associated with impaired cognition the following morning. The findings suggest that while melatonin is widely used as a sleep aid, it may carry next-day mental performance costs. This raises questions about the routine use of melatonin, particularly among younger populations who rely on sharp morning cognition. The research adds to growing scrutiny around the casual over-the-counter use of melatonin supplements.

0
ProgrammingDEV Community ·

Dev skips git commit after deploy, exposing a common release checklist blind spot

A software release was marked complete after all seven files were successfully transferred to a production server via scp and the live site reflected the new version. However, the developer had never committed or pushed the changes to the local git repository, leaving no record of the update in version control. The oversight went unnoticed until another team member checked the repository and flagged the missing commits. The incident highlights that file deployment and git version control are entirely independent operations, each requiring its own verification step. The recommended fix is to add an explicit git-sync check — using git status and git rev-list — as a separate item on the deployment checklist, distinct from confirming production availability.

0
ProgrammingDEV Community ·

Engineer Builds ETL Pipeline to Convert Apple Health XML into DuckDB Database

Apple Health data exports can produce multi-gigabyte XML files that are difficult to parse using standard tools like Excel or pandas. A data engineer has detailed a method to transform this raw export into a queryable DuckDB analytical database using Python, Apache Arrow, and lxml. The pipeline uses iterative XML parsing to process data in batches, avoiding out-of-memory errors that arise when loading large files entirely into RAM. Apache Arrow tables serve as an intermediate format, enabling efficient, zero-copy data transfer into DuckDB. The resulting database can then be queried with SQL and connected to visualization tools such as a Streamlit dashboard for personal health insights.

0
ProgrammingDEV Community ·

FireBall v3 Open-Source Tool Aims to Make AI-Generated Websites More Distinctive

A developer has released FireBall v3, an open-source design skill built to help AI coding and design agents produce less generic-looking websites. The tool addresses a common criticism that AI-generated interfaces tend to look visually identical, with repetitive layouts and styles. FireBall v3 introduces denser layouts, fewer rigid design constraints, and improved contextual adaptation so generated designs better reflect each project's purpose. The project is publicly available on GitHub, and the developer is actively seeking feedback from designers and developers. Two additional versions are already in planning, including one focused specifically on converting image references into websites.

0
ProgrammingDEV Community ·

CNCF Post Urges Teams to Treat AI Agents as Managed Identities with Formal Oversight

A CNCF community post by Matteo Bisi of ReeVo defines 'shadow AI' as any AI tool or agent used in the software development lifecycle without formal approval, ownership, risk assessment, or monitoring. Bisi argues that AI agents holding credentials capable of pushing code or restarting workloads pose serious security risks that Kubernetes cannot distinguish from malicious activity. The post maps six pipeline stages — from developer laptops to production clusters — each with its own failure modes, including prompt injection, secret leakage, and over-permissioned service accounts. Bisi recommends treating AI agents as a distinct identity class with named owners, short-lived scoped credentials, and a clear revocation path, backed by existing CNCF tools such as Sigstore, SPIFFE/SPIRE, Falco, and Argo CD. The core argument is that AI-authored artifacts and agent actions must be subject to the same attestation, RBAC, and runtime monitoring controls already available but widely underused.

0
ProgrammingDEV Community ·

Running LLMs Locally on a Laptop Is Now Practical, With Caveats

As of 2026, developers can run large language models locally on consumer laptops using tools like Ollama or LM Studio with minimal setup, a significant shift from the complex installations required just two years ago. The main draws are privacy, offline access, zero per-token costs, and full control over model versions. Hardware capability determines model quality: 8GB RAM supports basic 3–4B parameter models, 16GB handles more capable 7–9B models, and 32GB or a discrete GPU unlocks genuine reasoning with 20–30B models. Apple Silicon machines are particularly efficient due to unified memory shared between CPU and GPU. Key limitations include first-token load delays, higher confabulation rates in smaller models, RAM-heavy context windows, and speeds that lag behind cloud-hosted alternatives.

0
ProgrammingDEV Community ·

Model Context Protocol Emerges as Universal Standard for AI Tool Integration in 2026

The Model Context Protocol (MCP) has become the dominant standard for connecting large language models to external tools, eliminating the need to rewrite integrations each time a model is swapped. MCP operates as a client-server contract where servers expose tools, data resources, and prompt templates, while any compliant client — such as an IDE or AI agent — can communicate with them interchangeably. The protocol effectively decouples the tooling layer from the model layer, allowing developers to preserve their entire integration ecosystem when switching between AI models. Practitioners are advised to watch for risks including tool sprawl, prompt injection via server responses, overly broad permissions, and versioning drift between servers and clients. In a market where leading models change frequently, MCP is increasingly seen as the durable, strategic foundation for AI application development.

0
ProgrammingDEV Community ·

Why Always Using Flagship AI Models Is Now a Costly Mistake for Developers

For years, developers defaulted to using the most powerful AI models for every task, but in 2026 this approach has become a significant cost inefficiency. Smaller, cheaper 'flash-tier' models have begun outperforming flagship models on multi-step agentic coding benchmarks at a fraction of the price. Agentic workloads typically fan out into dozens of sub-tasks — most of which are simple enough for cheaper models — making blanket flagship usage wasteful in aggregate. Experts recommend a tiered routing strategy where flagship models handle only the 5–15% of steps requiring complex reasoning, while cheaper models carry routine tasks like classification, extraction, and formatting. Teams are advised to measure cost per completed task, log performance at each tier, and revisit routing decisions monthly as model capabilities and prices shift rapidly.

0
ProgrammingDEV Community ·

How a developer decided what to share between Next.js and Expo in a monorepo

A developer building SquadNote, a product with both a Next.js web app and an Expo mobile app, used a pnpm workspace and Turborepo monorepo to manage shared code. They found that tRPC types, design tokens, and pure business logic functions were strong candidates for sharing, as they have no platform-specific dependencies. However, UI components, authentication storage, and routing were kept separate because web and mobile environments impose different constraints and have different reasons to change. The developer recommends a checklist before extracting code into shared packages, asking whether the code depends on platform APIs and whether both apps would change it for the same reason. Their key takeaway is that the real value of a monorepo lies in the flexibility to shift sharing boundaries over time, not in maximising shared code from the start.

0
ProgrammingDEV Community ·

AI Prototyping Is Cheap, But Scaling Pilots Drains Budgets Without Strategy

A product leader managing an AI portfolio found that out of $1.2 million spent on annualized pilot run costs, only $340,000 in measurable value was produced, exposing a critical gap between experimentation and returns. The near-zero cost of building AI prototypes today — using tools like LangGraph and RAG pipelines — has removed the natural filter that once forced teams to prioritize only viable ideas. As a result, organizations now accumulate dozens of live pilots, each carrying ongoing infrastructure, security, and developer costs that quietly erode budgets. Research from HBR, including a study citing consumer goods firm Reckitt, found that spreading AI efforts across many small use cases yields only marginal efficiency gains rather than strategic transformation. The core argument is that AI portfolio discipline — choosing depth over breadth and measuring real business value — has become essential now that the barrier to prototyping has effectively disappeared.

0
ProgrammingDEV Community ·

Ouroboros Open-Source Tool Forces AI Coding Agents to Clarify Specs Before Writing Code

Ouroboros is an open-source, local-first runtime layer designed to address a common failure in AI-assisted coding: models making unchecked assumptions due to vague prompts. The tool sits in front of popular AI coding agents — including Claude Code, Codex CLI, and GitHub Copilot CLI — and replaces ad-hoc prompting with a structured five-stage workflow: interview, seed, execute, evaluate, and evolve. Before any code is generated, the system conducts a Socratic interview to surface hidden assumptions, then locks intent into an immutable specification only after ambiguity drops to 0.2 or below on a weighted clarity score. An automated three-stage evaluation gate checks output quality, while an evolutionary loop refines the specification across cycles until ontological similarity between consecutive generations reaches 0.95. The tool is installable via a single curl command and auto-detects the supported AI runtime in use.

0
ProgrammingDEV Community ·

Engineer shares hard-won lessons on robotics data pipelines from startup stint

A software engineer working a short-term trial role at an early-stage robotics startup encountered firsthand the real-world challenges of building data collection, annotation, and evaluation workflows. One key takeaway was the importance of simulating and testing pipelines with small data batches before scaling up, as skipping this step led to costly rework. The engineer also warned against over-designed annotation schemas, arguing that excessive labels increase operator errors and inconsistency, and that a minimal viable schema is more effective. On automation, the lesson was clear: automated checks serve as a useful filter but cannot replace manual spot-checking, especially in early pipeline stages. Though the trial role ended, the engineer framed the technical insights as transferable lessons applicable to any team working on robotics or machine-learning systems.

0
ProgrammingDEV Community ·

Stale Status Column Made AI Agent Believe Backlog Was 5x Its Actual Size

A publishing pipeline used by an AI agent fleet contained a ledger with a status column that tracked items as 'queued' but never updated them to 'published' after they were processed. Because no code was ever assigned to advance the status after publication, every item that had ever entered the queue retained the 'queued' label indefinitely. This caused the ledger to show 30 queued items when only 6 files were actually waiting in the queue directory. A working session reportedly read the inflated figure and concluded there was no urgency, deferring the task of restocking the queue. The error was not the result of deliberate design failure but of a silent assumption — the column recorded when an item became queued, but nothing ever recorded when that status ceased to be true.

0
ProgrammingDEV Community ·

Four Specialized AI Agent Skills to Improve Each Stage of Coding Workflows

A developer-focused article outlines four distinct AI agent skills designed to address different phases of a coding workflow rather than relying on a single catch-all prompt. The four skills — Caveman, Superpowers, grill-me, and handoff — each target a specific problem: concise execution communication, structured development, proposal pressure-testing, and context transfer between sessions respectively. The piece argues that using one large prompt across all stages often produces mismatched behavior, such as an agent being verbose when brevity is needed or missing key decisions buried in chat history. For example, grill-me interviews a developer one question at a time to surface hidden dependencies in a plan, while Superpowers guides an agent through a full specification-to-implementation cycle with test-driven development. The underlying principle is to apply the smallest useful constraint at the moment it prevents the most waste, rather than adding ceremony to every coding task.

0
ProgrammingDEV Community ·

Apple M5 Max Falls 11x Short of Real-Time Diffusion Video at 1.4 FPS vs 16 FPS Target

A developer benchmarking autoregressive diffusion video generation on an Apple M5 Max found the system produced just 1.418 native frames per second, far below the pre-defined real-time threshold of 16 FPS — an 11.28× gap. The tests used a Wan2.1-T2V-1.3B-based causal video model and were conducted under strict pre-registered protocols, with prompts, seeds, and thresholds locked before any results were seen. One meaningful systems improvement was identified: increasing MLX's bounded free-buffer cache from 1 GiB to 4 GiB cut total generation wall time by about 17%, from 69 to 57 seconds. Profiling revealed that causal VAE decoding alone accounted for 72–79% of total wall time, making the decoder — not the transformer — the primary bottleneck. The researcher published the findings and a reproducible verification repository despite missing the real-time target, arguing the measured bottlenecks and rejected hypotheses hold independent value.

0
ProgrammingDEV Community ·

Dev finds Chrome MV3 extensions can silently mishandle synced settings vs. local permissions

A developer building a Chrome Manifest V3 email-tracker blocker discovered that a single checkbox was masking three distinct types of state: user settings, actual host permissions, and active blocking rules. The issue surfaced during testing on a second Chrome profile, where synced settings indicated Gmail was enabled but the required host grant had not transferred, since Chrome Sync carries preferences but not optional permission grants. This mismatch caused the extension to behave as though access existed when it did not, either silently failing or incorrectly applying rules. The developer resolved this by explicitly checking chrome.permissions.contains() before activating any client, ensuring synced intent is never treated as confirmed access. The experience highlighted a gap in Chrome's documentation, which recommends optional permissions for user control but does not address preserving runtime state across syncs, revocations, and service worker restarts.

0
ProgrammingHacker News ·

Os8088 Brings Mac-Like Desktop Experience to Vintage IBM XT, 286, and 386 PCs

Os8088 is a newly showcased operating system designed to run on classic IBM hardware, including XT, 286, and 386 machines. The project aims to deliver a Mac-inspired graphical interface on these decades-old platforms. It was highlighted on Hacker News, where it attracted points and early community discussion. The OS appears targeted at retro computing enthusiasts seeking a modern-style user experience on legacy x86 hardware. Further details about its features and development status are available on the official website at os8088.com.

0
ProgrammingDEV Community ·

AI Agent Safety Depends on Harness and Governance Layers, Not Just Frameworks

A software developer argues that most AI agent architecture content focuses only on the framework layer — how an agent thinks — while neglecting two critical layers: the harness and governance. The harness controls how an agent acts, managing tool calls, budgets, retries, and sandboxing, while governance defines what an agent is permitted to do through policies, identity checks, and audit trails. Real-world failures, such as a support agent escalating database read access to execute deletions, are attributed not to reasoning errors but to missing controls at these layers. The author introduces a five-seam harness model with interception points before and after model calls and tool executions, and has tested 18 patterns across multiple frameworks including LangGraph. Key principles include treating tool calls as requests rather than actions, failing closed on unregistered tools, and encoding policy in code rather than prompts.

0
ProgrammingDEV Community ·

How WooCommerce Can Power Complex Event-Driven Business Workflows

WooCommerce is widely used as a standard e-commerce platform, but developers can architect it as an event-driven application engine where orders trigger broader business workflows rather than simply concluding a transaction. The key principle is keeping WooCommerce hook handlers thin, delegating actual business logic to dedicated service layers rather than embedding it directly in plugin code. Separating concerns across order, business, persistence, and integration layers makes applications easier to maintain and evolve independently of WooCommerce itself. A critical challenge in such systems is preventing duplicate event processing, which can cause repeated records, emails, or API calls, addressed through idempotency checks and state-aware transitions. Rather than reacting blindly to events, well-designed systems evaluate the current state of an entity before deciding what action to take.

← NewerPage 53 of 1115Older →