SShortSingh.

Programming

0
ProgrammingDEV Community ·

Retail Manager With No Degree Breaks Into Tech Through Free Coding Boot Camp

A 26-year-old grocery store manager with over five years in retail began searching for a career change in late 2022, feeling overworked and underpaid at $23 an hour. Despite being a high school dropout who later earned a GED, he had taught himself basic programming as a teenager but avoided pursuing tech due to a longstanding fear of mathematics. His father recommended a free coding boot camp — featured on 60 Minutes — that required passing entrance tests and signing a placement contract with partner companies. The program's entrance exams focused on critical thinking and problem-solving rather than arithmetic, which shifted his perspective on his own abilities. He began to recognise that skills built through years of retail work — communication, adaptability, and analytical thinking — could be directly applicable to a career in technology.

0
ProgrammingDEV Community ·

Dev Recovers Lost Gitea Data from Proxmox Backup After Docker Cleanup Mishap

A home lab user accidentally wiped their Gitea instance's repositories and user data while running a routine Docker cleanup on a Lenovo M920q mini PC. The data loss stemmed from a misconfigured bind mount that pointed directly into Docker's internal volume storage, causing the cleanup process to delete the volume as if it were unused. Rather than restoring an entire VM from backup, the user surgically extracted the needed directory by decompressing a Proxmox VMA backup, mounting the raw disk image via loop device, and navigating the LVM structure to retrieve the intact files. A corrupted SQLite database — likely caused by the backup running mid-write — was repaired using SQLite's built-in recovery mode. The setup was subsequently rebuilt with volume paths stored on a Synology NAS instead of inside Docker's internal storage to prevent a recurrence.

0
ProgrammingDEV Community ·

Why High ROE Can Be Misleading: Lessons from 200 US Companies

A finance professional new to Python used a Kaggle dataset of pre-calculated financial ratios for the top 200 US companies to explore what profitability metrics really reveal. Sorting companies by Return on Equity (ROE) placed McKesson Corporation at the top, but the result proved deceptive. McKesson's aggressive stock buybacks have shrunk its shareholder equity over the years, artificially inflating its ROE figure rather than reflecting genuine business outperformance. Comparing ROE alongside current ratio and debt-to-equity data showed that the 'best' company changes entirely depending on which financial question is being asked. The analysis underscores that no single ratio tells the full story, and that context — especially capital structure — is essential to interpreting financial health accurately.

0
ProgrammingDEV Community ·

How Machine Learning Works and Where It Shapes Everyday Life

Machine learning, a branch of artificial intelligence, enables computers to learn patterns from data and make predictions without being explicitly programmed for every scenario. It powers widely used tools such as search engines, voice assistants, fraud detection systems, and product recommendation platforms. The field relies on three core learning approaches: supervised learning, where models train on labeled data; unsupervised learning, where algorithms detect hidden patterns independently; and techniques like clustering and anomaly detection. Data quality is central to model performance, as biased, incomplete, or outdated training data can lead to flawed and potentially harmful outputs. Developers follow a structured pipeline of collecting, cleaning, and validating data before training and deploying models in real-world applications.

0
ProgrammingDEV Community ·

VNet Integration and Private Endpoints Resolve Azure Function App Runtime Failures

A developer encountered a persistent 'Runtime Unreachable' error while setting up a new Linux Azure Function App on the Elastic Premium EP1 plan in Microsoft Azure. The portal failed to display the runtime version and ZIP deployments were failing, with no application-level logs available since the app had never successfully initialized. The root cause was not in the application code but in network connectivity — the new Function App had not been connected to the existing shared Virtual Network, unlike other working Function Apps in the same environment. Because the associated storage account was protected by network restrictions and accessible only via private networking, the Function App could not reach the storage it needed for core runtime operations. The issue was resolved by integrating the Function App with the correct VNet and configuring a separate Private Endpoint along with Private DNS for the application's storage account.

0
ProgrammingDEV Community ·

Tether Gold Bridges Rated High Risk 8.3/10, Nine Critical Vulnerabilities Found

A security audit by a DeFi smart-contract research team, dated September 12, 2026, assessed the cross-chain bridge infrastructure of Tether Gold (XAU-T), which holds approximately $3.08 billion in total value locked across Ethereum, multiple Layer-2 networks, and non-EVM chains. The report identified nine critical attack vectors spanning smart-contract logic, bridge-relayer infrastructure, governance, and external dependencies, assigning an overall risk score of 8.3 out of 10. Among the most severe findings are a re-entrancy vulnerability in the mint function that could enable unlimited token creation, flawed Merkle proof verification susceptible to forged proofs, and an insufficiently secured multi-sig vault where two of five signing keys are controlled by the same legal entity. Additional risks include potential oracle manipulation that could trigger premature token releases and replay attack vulnerabilities allowing a single lock event to trigger minting across multiple Layer-2 networks. The researchers recommended immediate remediation of the highest-severity issues, followed by a phased security hardening roadmap.

0
ProgrammingDEV Community ·

Developer builds free tool to flag USPS hazmat fees before shippers buy labels

USPS can retroactively charge shippers a $50 hazardous materials noncompliance fee after a package has already been delivered, with no prior warning at the counter. A developer discovered the fee rules are spread across conflicting official documents — including Federal Register notices, Industry Alerts, and Postal Bulletins — that most sellers would never think to consult. In response, they built CanWeShip, a free pre-shipping compliance checker that lets users select a product type and receive side-by-side USPS, UPS, and FedEx verdicts with cited official sources. Unlike AI chatbots, the tool uses a deterministic rule engine backed by versioned, traceable rule sets, and explicitly flags gaps in information rather than guessing. A separate rule update also notes that USPS Returns shipments will become subject to the fee starting February 1, 2027.

0
ProgrammingDEV Community ·

Silent key update broke 40 verified records, exposing a gap in dual-tool checks

A developer discovered that 40 signed records failed verification after a cryptographic key row was edited in place rather than retired and replaced with a new entry. Both independent verification tools correctly reported failure, but neither could detect that the key material had changed since the records were originally signed. The root cause was a database row update that overwrote the public key and scheme fields under the same key ID, making legitimately signed records indistinguishable from forgeries. The issue went unnoticed for a day, highlighting that two independent tools share the same blind spots when both read from the same flawed source. The fix involved adding the retired key as a second row rather than deleting anything, and the writer was updated to loudly log key material on every run to surface future changes immediately.

0
ProgrammingDEV Community ·

Smart TVs Track Everything on Screen via ACR; Samsung and LG Settle Lawsuits

A 2024 study by researchers from UC Davis, University College London, and Universidad Carlos III de Madrid found that Samsung and LG smart TVs continuously capture on-screen content using Automatic Content Recognition (ACR), regardless of whether the source is a streaming app, live broadcast, or an external device connected via HDMI. Samsung TVs transmitted this data to company servers roughly every minute, while LG TVs did so every 15 seconds. In December 2025, Texas Attorney General Ken Paxton sued five major TV manufacturers — Samsung, Sony, LG, Hisense, and TCL — alleging ACR captures screenshots as frequently as every 500 milliseconds without adequate user consent. Samsung settled in February 2026, committing to obtain informed consent before collecting ACR data, followed by a similar LG settlement in May 2026, while cases against the remaining three manufacturers remain ongoing. Experts advise users to manually disable ACR-related settings — such as LG's 'Live Plus' — across multiple menu layers, as a single opt-out toggle is often insufficient.

0
ProgrammingDEV Community ·

AI Coding Tools Routinely Ship Broken Access Controls, Open-Source Scanner Aims to Prove Fixes Work

A common security flaw in AI-generated code allows any user to access another user's private data simply by changing an ID in a URL, because AI tools default to using service-role keys that bypass row-level security. This vulnerability has been observed repeatedly in apps built with tools like Lovable, Bolt, v0, Cursor, and Claude Code. An open-source scanner called auditai-scanner was built specifically to detect and verify fixes for this flaw, going beyond flagging potential issues by reproducing them in a sandboxed environment with synthetic test users. Rather than relying on the same AI model to both write and evaluate a fix, the tool independently confirms whether a cross-tenant data leak is actually closed before marking a finding as resolved. The project also generates a regression test from each reproduction, ensuring the vulnerability cannot be silently reintroduced in future code changes.

0
ProgrammingDEV Community ·

Agentic AI Coding Tools Demand Better Design, Tests, and Guardrails: Developers

Software engineers are expressing fatigue over AI hype, job market uncertainty, and the growing push toward agentic coding tools. While AI agents can rapidly modify large codebases, their effectiveness depends heavily on well-documented code, clear requirements, and defined success criteria. Without automated UI and integration tests, validating agent-driven changes at scale remains unreliable, posing risks to production stability. Quality assurance engineers are being urged to upskill in test automation to keep pace with aggressive AI-generated code changes. Despite concerns about an AI bubble, open-source LLMs are expected to persist, with companies increasingly likely to self-host models for internal use.

0
ProgrammingDEV Community ·

Developer Tests Three AI Coding Agents for 30 Days on Real Projects

A software developer spent 30 days evaluating Claude Code, GitHub Copilot CLI, and Cursor in agent mode on real-world projects, including a SaaS API, a data pipeline, and a legacy Node.js service. The tests showed significant time savings for boilerplate tasks, with routine REST endpoint generation dropping from 45 minutes to around 8 minutes. However, complex logic such as multi-step payment flows failed on the first attempt roughly 60% of the time, and agents performed poorly when debugging production-only bugs. Larger codebases caused context-tracking issues across all three tools, with agents occasionally referencing methods or types that no longer existed. The author concluded that AI coding agents offer genuine productivity gains for structured, repetitive work but still require human review for anything beyond straightforward scaffolding.

0
ProgrammingDEV Community ·

Researcher Built a Canary Executable to Spy on VirusTotal Sandboxes

A developer created a Rust-based executable with a fake identity — dubbed 'ZeroToken Engine' — and submitted it to VirusTotal to observe the analysis environments that ran it. The program collected metadata such as OS version, CPU and memory specs, uptime, hostname, and running process names, then reported findings via DNS heartbeats and HTTPS dossiers to the researcher's own infrastructure. It used two reporting channels: compact encoded DNS lookups and fuller CBOR-formatted HTTPS payloads, each tagged with a random eight-byte run ID. The experiment captured 353 event rows across 21 run IDs over a roughly five-hour window on September 12, 2026. The researcher noted that the binary installed nothing, harvested no credentials or documents, and intentionally disclosed the canary's true behavior in the project's README alongside its cover identity claims.

0
ProgrammingDEV Community ·

Safer AI Automations: Why a Validation Layer Should Sit Between AI and Action

A software developer has shared a design pattern aimed at making AI-powered workflows safer and more reliable in production environments. The core idea is to separate the AI's role — understanding unstructured user input and extracting key details — from the workflow's role of enforcing business rules and triggering actions. Under this approach, an AI model never directly executes critical operations; instead, its output is validated against predefined rules before any action is taken. Recommended safeguards include duplicate-action prevention, retry limits, timeouts, and a human handoff option when the AI is uncertain. The pattern can be applied across popular automation platforms such as n8n, Make, or custom API-based systems.

0
ProgrammingHacker News ·

A curated list of sci-fi books exploring how societies are built and justified

A reader has shared a personal selection of science fiction books centered on the theme of how human societies are constructed and rationalized. The list is published on BookDNA, a book recommendation platform. The post appeared on Hacker News, receiving minimal engagement with 4 points and no comments at the time of reporting. The collection appears aimed at readers interested in the sociological and philosophical dimensions of speculative fiction.

0
ProgrammingDEV Community ·

Why AI Chat Failover Needs Accessible Origin Announcements, Not Just Spinners

A developer discovered a critical accessibility flaw while conducting a keyboard-only audit of a streaming chat application: when the local inference path failed and silently switched to a remote server, screen readers and keyboard users received no indication of the origin change. The skeleton overlay that appeared during the failover stole focus and marked the main landmark as aria-busy, trapping assistive technology users without any announcement of where their data was being sent. The root cause was a single boolean state variable that treated local and remote streaming as identical, collapsing a meaningful privacy transition into a generic loading animation. The developer argues that the real defect is not the spinner's appearance but the absence of an origin state model that distinguishes on-device processing from remote server calls. A structured state table is proposed — covering idle, streaming-local, needs-consent, streaming-remote, error, and cancelled states — to ensure focus management, live region announcements, and user consent controls are all tied to where tokens actually originate.

0
ProgrammingDEV Community ·

Silent Citation Decay: How a Green Coverage Check Missed 23 Wrong Line Numbers

A developer discovered that all 23 line-number citations in a specification table were incorrect by one or two lines, yet an automated coverage check remained green throughout. The check only counted whether citation cells were non-empty, never verifying whether the references actually pointed to the correct content. The citations had been accurate when first written but silently drifted as other edits shifted line positions in the source file. To fix this, the developer replaced line-number-dependent references with quoted text snippets, allowing the tool to detect whether a citation had moved, gone missing, or remained valid. This shift from positional to keyed checking meant the system could now name the specific failing row rather than simply returning a misleading count of zero uncovered items.

0
ProgrammingDEV Community ·

Prompt Injection Is a Permissions Problem, Not a Model Problem

Prompt injection attacks occur when malicious instructions hidden inside documents — such as PDFs — manipulate an AI assistant into executing unintended actions, like leaking private files. The attack works because language models process user instructions and document content as a single stream of tokens, making it structurally difficult to distinguish intent from data. Common defences like system prompts and refusal training raise the cost of attacks but cannot eliminate the risk, since they operate within the same text-based substrate as the attack itself. The author argues that true security requires placing access controls outside the model entirely — in a permission table that no document content can modify or influence. This approach ensures that blocked files remain invisible to the model, that access decisions are looked up rather than reasoned about, and that every failed injection attempt is logged for review.

0
ProgrammingDEV Community ·

Zero-item audit phases falsely passed as 'AHEAD' due to vacuous logic flaw

A software audit tool incorrectly marked three phases as passing because they examined zero files, producing outputs like 'judged=0/0' and 'open=0' that technically satisfied pass conditions without measuring anything. The flaw stems from vacuous truth: rules designed to flag passing results fired correctly on empty data sets, making an unmeasured phase indistinguishable from a genuinely passing one. Unlike typical false positives, the output contained no suspicious numbers — the zeros were accurate, making the error nearly invisible. The developer resolved this by introducing a third audit state called VOID, distinct from pass or fail, to represent phases where no measurement was actually taken. Alongside this, enumeration and judgement logic were separated so that a zero result could be verified against whether data collection had genuinely occurred.

← NewerPage 1412 of 3335Older →