SShortSingh.

Programming

0
ProgrammingDEV Community ·

LayerByte Releases Entropyx, an Open-Source File Entropy Tool for Security Students

A developer under the handle LayerByte has released Entropyx, a free, open-source file entropy calculator designed exclusively for educational defensive security purposes. The C++ tool helps students understand static file analysis by comparing ordinary files against unusual binary samples using entropy as a key concept. Built with beginner readability in mind, it features clear validation, error handling, and intentionally excludes any offensive capabilities such as exploitation or malware behavior. The project is licensed under MIT and hosted publicly on GitHub as part of LayerByte's broader collection of focused, single-concept cybersecurity learning tools. The developer has invited community feedback, particularly suggestions that keep the project safe and suitable for classroom use.

0
ProgrammingDEV Community ·

DeepSeek's MLA Cuts KV Cache Memory by 93% Over Standard Transformer Attention

DeepSeek's Multi-Head Latent Attention (MLA), used in DeepSeek-V2 and V3, dramatically reduces the memory footprint of the key-value cache during transformer inference. Instead of storing full key and value tensors for all attention heads, MLA compresses the hidden state into a low-dimensional latent vector of just 512 scalars per token. This brings the KV cache cost down to roughly 135 KB per token in FP16, compared to 3.84 MB for a standard multi-head attention model like DeepSeek's 67B baseline — a reduction of over 93%. The improvement directly addresses the memory-bandwidth bottleneck that limits token generation speed during the autoregressive decode phase. By contrast, competing approaches like Multi-Query Attention achieve similar compression but at a measurable cost to model quality, making MLA a more efficient trade-off.

0
ProgrammingDEV Community ·

Patched Claude Code Flaws Allowed API Key Theft and Code Execution Before Trust Prompt

Two security vulnerabilities, CVE-2026-21852 and CVE-2025-59536, were discovered in Anthropic's Claude Code CLI tool affecting versions prior to 2.0.65. The flaws stemmed from an order-of-operations defect in which the CLI merged project-level configuration files before presenting users with a trust confirmation prompt. This pre-trust execution window allowed a malicious repository to silently redirect API requests to an attacker-controlled server, exposing the developer's Anthropic API key in plaintext. Beyond credential theft, the same window enabled attackers to embed malicious lifecycle hooks in repository config files, triggering arbitrary code execution on the developer's machine at session start. The vulnerabilities were addressed in version 2.0.65, which enforces directory trust evaluation before any project-level configuration is loaded or executed.

0
ProgrammingDEV Community ·

Why AI Code Gets Less Scrutiny Than a npm Package, and Why That's a Problem

A software engineer argues that development teams apply rigorous checks — lockfiles, checksums, signed commits, and code review — to human-written code but routinely skip equivalent scrutiny for AI-generated output. The core concern is not that models hallucinate obvious errors, which existing tooling tends to catch, but that they produce fluent, well-cited responses even when the underlying logic is wrong. The author illustrates this with a real case where a model correctly cited a documented Odoo rule yet still implemented it incorrectly, showing that citation accuracy does not equal rule compliance. The piece frames AI as a 'fluency machine' — one that mimics the surface signals of confidence and correctness without providing a genuine uncertainty indicator. The author concludes that the real challenge is redefining what counts as 'checked' when the author of the code cannot be questioned, held accountable, or expected to hedge when unsure.

0
ProgrammingDEV Community ·

Why passing a code check and recording the truth are not the same goal

A developer running a semantic checker on a codebase encountered 11 unrecognised identifiers, which could apparently be resolved by adding all 11 entries to a single vocabulary file. On closer inspection, the identifiers belonged to two distinct categories — six module-level instruments and five layer-level symbols — each requiring a separate registry with different meanings and downstream readers. Bulk-declaring all entries in one place would have cleared the check but silently introduced false data, misleading other tooling about what operations a module actually performs. Even after the correct two-file fix was made, the checker continued reporting errors because it reads a generated artifact rather than the source declarations directly, requiring a commit-then-regenerate cycle before results reflect reality. The author concludes that a passing check and an accurate codebase are different goals, and when they conflict, the check — as a downstream artifact — should be treated as subordinate to the truth.

0
ProgrammingDEV Community ·

How to Build a 24/7 Voice AI Booking Agent Using Vapi, ElevenLabs, and n8n

A technical guide published on DEV Community outlines how to build a fully automated voice AI appointment booking system by integrating Vapi's speech recognition, ElevenLabs' text-to-speech, and an n8n workflow. The system can answer calls, extract booking intent, create Google Calendar events, send SMS confirmations via Twilio, and deliver AI-generated voice reminders. Most core tools are available on free tiers, with optional paid components like Twilio's pay-as-you-go SMS and n8n's cloud plan at $20 per month. The estimated build time is six to eight hours, covering account setup, workflow configuration, and testing. The guide targets developers looking to deploy a production-ready scheduling assistant without building custom infrastructure from scratch.

0
ProgrammingDEV Community ·

Facade Pattern: How One Design Pattern Tames E-Commerce Checkout Complexity

The Facade Pattern is a software design approach that hides the complexity of multiple subsystems behind a single, simplified interface. In a typical e-commerce checkout flow, a controller must coordinate four separate services — inventory, payment, shipping, and notifications — each with its own API and error handling. Without a Facade, any change to one of these APIs forces developers to hunt down and update scattered code across the entire project. By introducing an OrderCheckoutFacade with a single finalizarPedido() method, the controller only interacts with one class, reducing tight coupling and making unit testing significantly easier. A Java implementation demonstrates how the Facade orchestrates all four service clients internally while keeping the rest of the application unaware of the underlying complexity.

0
ProgrammingDEV Community ·

Doop lets AI agents co-design on a live canvas, but free use has strict limits

Doop is an open-source multiplayer design canvas, created on 22 August 2026, that allows both humans and AI agents to edit the same HTML-rendering canvas simultaneously in real time. Unlike most AI-assisted design tools, Doop embeds a Model Context Protocol (MCP) server directly into the project, enabling standard connections to agents such as Claude Code or OpenAI Codex without custom adapters. The platform includes live cursors, avatar presence indicators, and a shared activity feed that logs every action by both humans and agents over a single WebSocket room. However, the built-in Doop Agent does not run for free by default — the RESIDENT_TASK_LIMIT variable is set to 0, meaning users must connect a ChatGPT account or provide an OpenAI API key before any real agent task can execute. The project is licensed under AGPL-3.0, requiring anyone who publicly hosts a modified version to release those changes under the same licence, and the Doop name and logo are trademarked separately from the code.

0
ProgrammingDEV Community ·

Phantom Friday checkout crashes traced to forgotten canary deployment instance

A checkout service began throwing intermittent server errors most Friday afternoons, with all symptoms disappearing by Monday, making the bug extremely difficult to reproduce or diagnose. Initial investigations ruled out long-running queries, connection leaks in a newly shipped reporting endpoint, and rogue scheduled jobs as potential causes. The real culprit turned out to be a forgotten third service instance left over from a canary deployment experiment months earlier, which was no longer receiving live traffic and therefore invisible in standard metrics. This dormant instance had a faulty health-check routine that opened a fresh database connection every few seconds without reusing the pool, steadily exhausting the connection limit. An auto-scaling policy restarted the instance every Monday, resetting the leak and explaining the precise weekly pattern engineers had struggled to pin down.

0
ProgrammingHacker News ·

Docket Tool Creates Per-Commit Evidence Records for AI-Generated Code

Docket is an open-source tool published on GitHub by developer Dillonsmart that generates evidence records tied to individual code commits. It is designed specifically to document and track code written by AI agents. The tool addresses growing concerns around accountability and auditability in software development as AI-assisted coding becomes more widespread. By attaching structured records to each commit, Docket aims to provide a verifiable trail of how and why code changes were made.

0
ProgrammingDEV Community ·

How to Verify Which Python Binary Your Code Actually Runs

Developers often assume commands like 'python' or 'pip' point to the correct interpreter, but this can silently cause errors in scripts and CI pipelines. On many systems, 'python' is either missing or aliased differently from 'python3', making explicit checks essential. Virtual environments add another layer of confusion, as a new shell session may not activate the venv even if the directory exists. Similarly, 'pip' and 'python3 -m pip' can belong to different interpreters, leading to packages being installed in the wrong environment. A short shell audit script using commands like 'command -v', 'sys.executable', and exit code checks can quickly confirm which binaries are actually in use.

0
ProgrammingDEV Community ·

GitHub Copilot Can Now Formally Approve Pull Requests, Counting Toward Branch Rules

GitHub updated its Copilot code review tool on 1 September 2026, allowing it to submit approvals that count toward a repository's required-approvals rule, the same way a human teammate's approval would. Previously, Copilot only left advisory comments and its reviews explicitly did not satisfy branch protection requirements. Administrators must actively enable the feature, and the approval is automatically dismissed if new commits are pushed, mirroring existing human-review behaviour. A follow-up update on 11 September added shell-tool execution during reviews, auto-resolution of Copilot's own comments, and an ensemble of agents that GitHub says improved detection of high-severity issues by 47%. The changes are currently in public preview and subject to change, raising governance questions about how AI approvals interact with enterprise and repository-level branch protection policies.

0
ProgrammingDEV Community ·

Opik: Open-Source LLM Observability Tool Lets Teams Self-Host Agent Tracing

Opik is an open-source, self-hostable observability platform for LLM agents, first created on May 10, 2023, and actively maintained with over 7,000 commits as of September 2026. The tool allows developers to trace every decision an agent makes before a failure occurs, addressing the common problem of discovering errors only after users complain. Licensed under Apache-2.0, Opik can be deployed entirely within a team's own infrastructure, with no data leaving the system and no enterprise sales process required. Beyond basic tracing, the platform bundles LLM-as-a-judge evaluation, prompt management, RAG assessment, guardrails, and CI/CD integration via PyTest into a single suite. Coding agents such as Claude Code, Cursor, and VS Code Copilot can also connect directly to Opik to read traces and run evaluations from within a chat interface.

0
ProgrammingDEV Community ·

Developer flags self-asserted test steps and untestable surfaces in E2E run

A developer running end-to-end tests on a sandbox project reported a 10/10 pass rate, but noted that one of the ten steps could not be externally verified — it was explicitly labelled as self-asserted rather than silently marked green. The untestable property concerned whether the binary correctly refuses unknown operation names, a check that is impossible to automate because the command interface has no argument slot through which a bad operation name can be passed. The developer argues this is a product observation, not a test limitation: if something cannot be tested from outside, it often also cannot be used from outside, and both gaps share the same fix. The remaining nine steps were validated across two independently created sandboxes, with all 46 output lines matching byte-for-byte, made possible by deriving environment identifiers from content rather than random allocation. An additional hour was lost to Git Bash silently rewriting POSIX paths before they reached the program, a transformation that produced no error and caused failures far from the actual source.

0
ProgrammingDEV Community ·

Developer Builds Immutable Invoice API Where Corrections Create New Documents

A developer published a TypeScript/Express REST API that enforces a strict invoice lifecycle, making finalized invoices immutable and handling corrections by issuing new replacement documents rather than editing originals. The system uses four states — draft, issued, canceled, and replaced — with replacement operations wrapped in a single database transaction to prevent inconsistent states. Despite achieving over 97% test coverage across 56 tests, two real bugs slipped through undetected by automated testing. One bug involved incorrect currency division that rendered Vietnamese Dong amounts as hundredths of their actual value on generated PDFs, a mistake the tests missed because both the code and expected test values shared the same flawed assumption. The incident highlights a key limitation of unit testing: automated tests confirm code behaves consistently with developer expectations, but cannot catch bugs rooted in incorrect assumptions themselves.

0
ProgrammingDEV Community ·

Developer Builds Local Tool to Filter SAM.gov Contractor Data Without API Limits

A developer has created the SAM.gov Public Contractor & NAICS Database Compiler, a tool designed to make the federal government's public bulk contractor dataset more accessible and searchable. The tool processes SAM.gov's official bulk extract locally, eliminating dependence on external API calls or third-party platforms. Users can filter contractor records by criteria such as NAICS codes, state, small-business status, CAGE code availability, and SBA classifications. Results can be exported to Excel or CSV, either as individual registration records or consolidated by unique entity. The tool is available as a standalone Windows executable and also supports a Python-based workflow for more technical users.

0
ProgrammingDEV Community ·

Misleading Error Code Hid a Missing Config Line, Not a Broken Parser

A build tool repeatedly reported a parse failure on a requirements document, leading developers to suspect either a malformed file or a broken parser — but both were intact. The real cause was a missing one-line declaration in the configuration, which meant the reader treated all 256 structured data rows as plain prose and found nothing to parse. The incident highlighted how error codes that name the stage of failure, rather than the underlying cause, can send investigators in the wrong direction. A second issue emerged during the fix: regenerating derived artifacts over a working tree with uncommitted edits produced inconsistent, non-reproducible results across consecutive runs. The author concluded that derived artifacts should only be generated and committed from a clean, committed state to ensure reproducibility.

0
ProgrammingDEV Community ·

Kairos Scheduler Offers Calendar-Aware Alternative to Cron for Complex Job Schedules

A developer tutorial published on DEV Community introduces Kairos, a scheduling tool designed to handle calendar-aware job scheduling that traditional cron cannot manage natively. Unlike cron, Kairos can account for time zones, public holidays, and business-day logic directly within schedule definitions, eliminating the need for wrapper scripts to handle edge cases. The article walks through five practical scheduling patterns — including business-day-only runs, true month-end detection, and payroll-style rolling dates — using 2026 US federal holidays as a reference dataset. Kairos does not replace a job runner such as systemd or a task queue; instead, it acts as a decision layer that determines whether a scheduled trigger should actually fire on a given day. The author recommends sticking with plain cron for simple fixed-interval tasks and adopting Kairos only when calendar complexity justifies the migration.

0
ProgrammingDEV Community ·

Kairos 1.0 launches as a schedule language built for composable business-day logic

A developer has released version 1.0 of Kairos, an open-source scheduling language designed to express complex date rules such as '3 business days before month-end' as composable expressions. Unlike existing tools such as cron or RRULE, Kairos allows calendar systems, holiday rules, and fiscal calendars to be user-defined rather than hard-coded. The reference implementation runs entirely client-side and derives observed holiday dates algorithmically, with no pre-built lookup tables. Evaluation is a pure function, making missed schedules enumerable and audit trails reproducible. The language has seen production use over the summer and is available via npm, with documentation and an English specification published at kairos-lang.org.

0
ProgrammingDEV Community ·

Developer Builds Reusable Python CLI Toolbox to Replace Repetitive AI-Generated Scripts

A Node.js developer built a Python command-line toolbox called Toolbox after growing tired of generating and discarding one-off AI-written scripts for routine tasks. The project, published on GitHub, handles file and image operations including CSV-to-Excel conversion, image grayscale, blur, compression, and PDF compression via rasterization. Built after completing a freeCodeCamp Python certification, it served as a practical way to apply new skills beyond just earning the certificate. The developer used the modern package manager uv to manage dependencies and virtual environments, finding its workflow closely mirrored familiar Node.js tooling. Standard library modules like argparse and csv were used alongside third-party packages Pillow and OpenPyXL to keep the toolbox lightweight and maintainable.

← NewerPage 1368 of 3313Older →