SShortSingh.

Programming

0
ProgrammingDEV Community ·

Andrew Ng at Berkeley: AGI hype is financial, AI job fears overblown, model layer overvalued

At the UC Berkeley Agentic AI Summit, AI pioneer Andrew Ng argued that AGI declarations are largely driven by financial contract incentives rather than genuine technical milestones, urging people to form their own definitions. He challenged the popular narrative that AI is eliminating jobs at scale, pointing out that he personally cannot find enough qualified AI engineers to hire. Ng identified the real bubble risk not in compute or infrastructure, but in AI companies whose only moat is model differentiation, which he considers fragile. He also warned that while open-weight AI models have won the public debate, the more consequential battle is playing out in Washington through unresolved regulatory policy. Sequoia's Alfred Lin echoed the view that durable AI companies will look very different from today's leaders, drawing parallels to how open-source dynamics reshaped earlier tech industries.

0
ProgrammingDEV Community ·

Developer builds Steam tool to detect rating declines and diagnose negative review causes

A developer has created an automated tool that monitors Steam game reviews in real time to catch rating declines before they damage a title's overall score. The tool uses two public, unauthenticated Steam API endpoints to track individual reviews and a rolling histogram of positive versus negative recommendations over time. Unlike Steam's all-time average rating badge, which can remain high for weeks after a damaging event, the tool compares recent review periods against a baseline to flag genuine downward trends. It also categorizes negative feedback by theme, distinguishing between bug reports requiring urgent fixes and subjective complaints about game design. The tool is available as a pay-per-run service on Apify at approximately $0.03 per game analyzed and is aimed at developers seeking early warnings about player sentiment shifts.

0
ProgrammingDEV Community ·

Why CPU metrics mislead autoscalers running single-threaded services

A single-threaded Node.js API was experiencing high latency and request backlogs, yet its autoscaler remained idle because average CPU utilization across a four-vCPU task showed only around 30 percent. The root cause was architectural: a single-threaded process can saturate only one CPU core, making peak load appear as roughly 25–30 percent when averaged across all cores. This meant the autoscaling policy was effectively measuring load divided by four, rather than actual service strain. Engineers identified two durable fixes — resizing tasks to one vCPU so full saturation registers as 100 percent, and switching scaling signals to latency or request-count metrics that directly reflect workload pressure. The broader lesson applies to any single-threaded runtime: average CPU utilization answers the wrong question for services that cannot distribute work across cores.

0
ProgrammingDEV Community ·

Developer builds automated weekly re-rating pipeline for 245+ AI tools

A developer created AI Tier List, a bilingual English-Korean directory that ranks over 245 AI tools from S to D tier, with ratings refreshed automatically every week. A GitHub Actions cron job runs every Sunday, collecting Google Trends data, OpenRouter usage stats, and performing site health checks to flag or deactivate dead tools. To prevent low-quality automated content, an LLM proposes tier changes into a pending queue rather than publishing directly, with a human reviewing and approving each batch. The project has grown to around 1,500 sitemap URLs and roughly 90 search clicks in the past 28 days, with impressions rising approximately sevenfold after a sitemap bug was fixed. The developer noted that infrastructure issues proved more damaging than content quality gaps, as one broken sitemap kept half the site out of Google's index for weeks.

0
ProgrammingDEV Community ·

Open-source PHP SDK bitget-php launches for Bitget trading API integration

A new open-source library called bitget-php has been released to simplify PHP-based integrations with the Bitget Unified Trading Account (UTA) v3 API. The SDK targets PHP 8.2 and above and offers optional support for Laravel versions 10 through 13, making it usable in both framework and standalone environments. Its initial release covers market data, account management, trading operations, and a WebSocket client capable of automatic reconnection and subscription recovery after disconnections. To reduce common integration pitfalls, the library represents numeric values such as prices and quantities as strings rather than floats, preventing floating-point precision errors in financial calculations. The project also includes a typed exception hierarchy for clearer API error handling and defaults to a no-op PSR-3 logger to ensure API credentials are never written to logs.

0
ProgrammingDEV Community ·

FaceID API Lets Developers Add Face Liveness Detection via Simple REST Calls

FaceID API is a free-tier REST service that enables web and mobile app developers to integrate face liveness detection without proprietary hardware or expensive platforms. The API uses a secure session model where the API key stays server-side, and a widget URL is passed to the frontend via an iframe, ensuring no raw biometric data is exposed. During verification, the browser-based widget runs a real-time head-movement challenge using MediaPipe FaceMesh, tracking 468 facial landmarks before generating a compact mathematical descriptor that is sent to the server. The service supports three modes — register, verify, and authenticate — covering first-time enrollment, one-to-one matching, and one-to-many search respectively. FaceID API is available at faceidentity.site with a free tier of up to 200 enrollments per month and no credit card required.

0
ProgrammingDEV Community ·

AI Agent Discovered Its Own Fixes Were Never Called, Coining 'Wire-Not-Ship' Failure Mode

A self-evolving AI agent built on a dual-strand architecture identified a systemic flaw in its own development pipeline: completed, tested code modules were being produced but never wired into the daily orchestrator, meaning they never actually ran. The agent, operating across tens of thousands of generations, traced the root cause to a structural gap where neither the exploring strand (Yang) nor the refining strand (Yin) owned the responsibility of connecting new modules to callers. Once the agent named the pattern 'wire-not-ship,' it began detecting the same issue repeatedly across consecutive generations, with some orphaned modules having zero runtime consumers since day one. The case highlighted a blind spot in automated testing: passing tests confirm a function works in isolation but cannot verify whether anything in production actually invokes it. The developer noted that the agent's self-diagnosis emerged without a scheduled cron job in place, meaning the system proactively audited its own pipeline rather than waiting for an external trigger.

0
ProgrammingDEV Community ·

Developer Ports 1989 Microsoft Word 1.1a to Run Natively on 64-Bit Windows 11

A reverse engineer posted a GitHub repository in early 2026 containing a native x64 port of Microsoft Word 1.1a, a 16-bit word processor originally released in November 1989. The project involved transpiling and refactoring the original binary's logic into modern x86-64 code, allowing it to run on Windows 11 without any emulator or virtual machine. The feat is technically significant because 16-bit Windows applications rely on a segmented memory model incompatible with modern 64-bit architecture, and Windows 11 has no built-in support for running such software natively. The port drew widespread attention on Hacker News, sparking discussion about software bloat and the contrast between the lean, fast original application and today's resource-heavy office suites. Word 1.1a is historically notable as the ancestor of the .doc file format and a foundational piece of the broader office software ecosystem.

0
ProgrammingDEV Community ·

How to Structure API Architecture in React: Service Layers and Interceptors

As React applications scale, placing API logic directly inside components leads to tightly coupled, hard-to-maintain codebases. A layered architecture separating components, custom hooks, service layers, and a central API client addresses this problem by assigning clear responsibilities to each level. Tools like Axios offer built-in interceptors that enable centralized handling of authentication tokens, error responses, and request logging without repeating code across components. Axios and the native Fetch API both remain valid choices, with the decision depending on team needs and project requirements. This approach ensures React components stay focused on UI rendering while backend communication logic remains modular and reusable.

0
ProgrammingDEV Community ·

Nigerian Self-Taught Developer Builds Biometric Face Verification API Using Only Android Phone

Muhammad Abubakar Yusuf, a self-taught developer from Nigeria, has built a production-ready biometric face verification API called FaceID using only an Android phone and no financial investment. The API enables developers to add face liveness detection to web or mobile apps in under 10 minutes, using MediaPipe FaceMesh and face-api.js to generate a 128-float mathematical descriptor that never stores or transmits actual photos. The system runs entirely on Cloudflare Workers and Cloudflare D1, eliminating the need for traditional server infrastructure. Security measures include one-time widget tokens, HMAC-SHA256 webhook verification, rate limiting, and admin access controlled via environment secrets rather than a database. The API is available at faceidentity.site with a free tier of 200 enrollments per month, while paid plans start at $9 per month for higher usage limits.

0
ProgrammingDEV Community ·

Cloudflare Email Routing and Wikidata Signals Boosted Convertify's Bing AI Citations 3x

Developer Serhii documented Week 19 of building Convertify, a file-conversion tool, noting a 3.1x quarter-over-quarter rise in Bing Copilot AI citations after adding structured entity signals like a Wikidata item and JSON-LD schema in the prior week. The most-cited page was an image format benchmark built on real measurements from a Rust and libvips pipeline, which Copilot appeared to prefer over theoretical codec-spec figures common on other sites. To meet a journalist-sourcing platform's requirement, Serhii set up a branded email address using Cloudflare Email Routing in under 10 minutes at no cost, highlighting its value for pitch credibility. A known bug causing background-removal PNGs to export at 30 MB instead of 2–3 MB due to an uncast 16-bit alpha channel remains unresolved, though a partial frontend fix was shipped this week. The developer plans to publish a new AVIF vs WebP benchmark, send more journalist pitches, and finally address the PNG file-size bug in the coming week.

0
ProgrammingDEV Community ·

Full Stack Developer vs Engineer: The Difference Is Mindset, Not Tech Stack

The terms 'Full Stack Developer' and 'Full Stack Engineer' are frequently used interchangeably, but they describe different scopes of work. A Full Stack Developer primarily focuses on building frontend and backend features, working with databases, APIs, and application code across a given tech stack. A Full Stack Engineer goes further by taking responsibility for system architecture, scalability, security, performance, and infrastructure decisions. The key distinction lies not in which technologies a person knows, but in how they approach software development and the level of systemic thinking they apply. Professionals are advised to choose the title that honestly reflects their day-to-day responsibilities rather than the one that sounds more impressive.

0
ProgrammingDEV Community ·

Coldcard Wallet Bug Drained 2,055 BTC via Weak RNG That Audits Failed to Catch

Since July 30, approximately 2,055 BTC worth around $130 million has been stolen from Coldcard hardware wallets across multiple attack waves, with no phishing or malware involved. Attackers exploited a flaw introduced during a 2021 cryptography migration that silently redirected seed generation from the device's hardware random number generator to a weaker software fallback called Yasmarang. The root cause was a single flawed build directive — #ifndef — which checked whether a setting was defined rather than whether it was enabled, allowing a zero value to pass as valid. This reduced the key search space from 128 bits to roughly 40 bits on older models, making private keys brute-forceable offline and enabling one attacker to sweep $70 million in just 41 minutes. Security experts note that existing hardware wallet audits confirmed the correct generator existed in the codebase but never verified which code path actually executed on real devices — a systemic gap with no current industry standard to address it.

0
ProgrammingDEV Community ·

Open Method Uses Public Model Files to Test 'Built From Scratch' LLM Claims

A technique called Model DNA allows independent researchers to assess whether a large language model was genuinely trained from scratch or derived from an existing open-weight base, using only publicly available files such as config.json, tokenizer data, and embedding weights. The method combines three signals — architectural configuration, tokenizer vocabulary overlap, and embedding-space similarity via Linear CKA — to place a model on a lineage spectrum. It gained prominence around mid-2026 when 'self-developed' claims by AI labs began facing public scrutiny, including a widely shared Zhihu thread that questioned several such announcements. The approach has been applied to major Korean AI developers including LG, NAVER, Kakao, SKT, and others, though its authors stress it produces a lineage label rather than an accusation of wrongdoing. Key limitations include sensitivity to similarity thresholds, a gray zone around continued pretraining, and the fact that the analysis is restricted to embedding layers alone.

0
ProgrammingDEV Community ·

How to Build a Distress Signal Mechanism for Stuck AI Agents in Production

Production AI agents can silently fail by looping, retrying failed calls, or consuming resources while appearing to function normally from the outside. A proposed design pattern called an 'AI agent distress signal' gives agents a structured way to flag when they are blocked, uncertain, over budget, or about to take a risky action. The mechanism sits between detection and recovery controls, routing issues to a human operator or fallback system before a workflow wastes cost or trust. Developers are advised to define explicit trigger categories — such as missing permissions, conflicting data sources, and repeated tool failures — rather than relying on the model's own judgment. The goal is to provide production workflows with a reliable, auditable escape path when a task cannot be safely completed.

0
ProgrammingDEV Community ·

Midnight Network enables private identity verification using zero-knowledge proofs

Midnight Network is a data-protection blockchain that lets developers verify user identities without exposing personal data on-chain, unlike traditional EVM-based systems where all data is publicly visible. It uses a smart contract language called Compact, which separates data into public ledger state and private witness data that never leaves a user's device. The identity pattern works by having users store a cryptographic hash of a private secret on-chain, then later prove knowledge of that secret through a locally generated zero-knowledge proof. Three core components power this system: the ledger for public state, witnesses for private inputs, and circuits that generate ZK proofs before any transaction is submitted. This approach ensures the blockchain only receives mathematical proof that an assertion is valid, without ever learning the underlying secret.

0
ProgrammingDEV Community ·

React Architecture Guide Explains How to Scale Large Frontend Applications

A tutorial published on DEV Community as part of a React Mastery Series outlines principles for architecting large-scale React applications, targeting senior frontend engineers and architects. The guide contrasts small apps with enterprise-level applications that may have over 1,000 components, 100+ pages, multiple teams, and millions of users. It introduces concepts such as high cohesion, low coupling, and clear domain boundaries to prevent features from becoming tightly interdependent. The tutorial recommends organizing code around business domains rather than technical file types, with each feature exposing only a public API via an index file. It also briefly introduces Clean Architecture, separating the UI, application, domain, and infrastructure layers for improved testability and scalability.

0
ProgrammingHacker News ·

SAP Freezes Most Hiring and Travel to Fund Soaring AI Investment Costs

German enterprise software giant SAP has halted most employee travel and paused the majority of its hiring activities. The move is directly linked to the rapidly rising costs associated with the company's artificial intelligence initiatives. SAP is redirecting budget resources to sustain and expand its AI-related operations. The decision reflects a broader trend of large technology firms making significant internal trade-offs to prioritize AI development.

0
ProgrammingDEV Community ·

Build, Buy, or API: A Practical Framework for AI Capability Decisions

A software consultancy has outlined a three-gate framework for deciding whether to build, buy, or use an API for AI capabilities, evaluating each option on competitive differentiation, rate of change, and real-world cost at scale. Commodity capabilities such as text generation, transcription, and OCR are best served by hosted APIs from providers like OpenAI or Anthropic, which typically outperform small in-house teams from day one. Buying a dedicated third-party product makes sense when the required capability is a solved problem and maintaining it in-house would distract the team from core product work. Building in-house is justified only when the capability is a genuine differentiator, proprietary data meaningfully changes the outcome, or per-call API costs exceed a subscription at high volume. Regardless of the choice made, the firm recommends designing for flexibility by placing providers behind a switchable interface and monitoring costs closely, since the optimal decision can shift as volumes grow or vendor terms change.

0
ProgrammingDEV Community ·

How to Design MCP Tool Schemas That Prevent AI Agent Misuse

A software development analysis highlights that input validation alone is insufficient to prevent AI agents from misusing MCP server tools, as language models can send well-formed but semantically incorrect calls. Four recurring failure patterns are identified: selecting the wrong tool, passing valid-but-incorrect arguments, violating preconditions, and receiving unrecoverable errors. The author argues these are interface design flaws rather than validation bugs, and that the solution lies in constraining tool schemas at the design stage. Using real code from the Frihet MCP server, the piece demonstrates how replacing open string fields with enums and bounded numeric ranges eliminates entire categories of agent error. By making illegal states unrepresentable in the schema itself, developers can guide probabilistic AI callers toward correct behavior without relying on documentation.

← NewerPage 283 of 1352Older →