SShortSingh.

Programming

0
ProgrammingDEV Community ·

AI Writes Code Fast, But Verifying It Is Now the Real Engineering Challenge

As AI tools make code generation nearly instantaneous, software engineering teams are discovering that evaluation and validation have become the true bottleneck in shipping reliable software. One engineering team spent six days diagnosing a subtle bug after AI-refactored search indexing code mishandled UK VAT-inclusive pricing logic — saving 16 hours of coding but costing over 60 hours of incident investigation. The root cause was not flawed code syntax but missing institutional knowledge about how a legacy order management system actually behaved. The author argues that traditional velocity metrics like tickets closed and lines shipped are now actively misleading, as they incentivize volume over verified correctness. The new priority for engineering teams should be building robust evaluation infrastructure — including shadow deployments, regression suites, and observability tooling — before AI-generated code reaches production.

0
ProgrammingDEV Community ·

Cameroonian Students Build YouthTrend, a Unified Social Network for University Life

YouthTrend is a national social networking platform designed for university students in Cameroon, aiming to replace the fragmented use of WhatsApp groups, Telegram channels, and email lists. The platform offers a unified feed where students can discover people, clubs, and events across all participating schools. Users are verified through their universities, while staff or senior students can manage official school profiles. Built as a modular monolith using React and Vite, the project originated as coursework and has since grown into a documented product with formal technical specifications. The team is still weighing key decisions, including the student verification method and whether a native mobile app should be part of the initial release.

0
ProgrammingDEV Community ·

Recursive vs Iterative Tree Traversals: Understanding the Stack Behind the Magic

Tree traversals are a common interview challenge, and many developers rely on recursive solutions without fully understanding how they work under the hood. The core insight is that recursive traversal uses the call stack to track return points, and this behavior can be replicated with an explicit stack data structure. In an iterative inorder traversal, nodes are pushed left as far as possible, then popped and visited before moving to the right subtree — mirroring the recursive left-node-right pattern. This approach avoids stack overflow errors that can occur with deeply skewed trees containing large numbers of nodes. Two common pitfalls in iterative implementations are failing to advance the current pointer after popping a node, and pushing children in the wrong order, both of which can cause incorrect output or infinite loops.

0
ProgrammingDEV Community ·

Free Health Calculator Portal Quantas Calorias Prioritises Transparency Over Raw Numbers

Quantas Calorias is a free web portal that consolidates multiple nutrition and health-screening calculators, including BMI, basal metabolic rate, cardiovascular risk, and older-adult vulnerability tools, into a single interface. The platform was built around the principle that health calculations are only useful when users understand both what the numbers mean and what their limitations are. Developers focused on designing plain-language explanations that make uncertainty visible within each tool rather than burying disclaimers in footnotes. The portal draws a clear line between educational use — such as preparing questions for a doctor — and clinical decision-making, explicitly discouraging users from starting or stopping medication based on results. Quantas Calorias is publicly accessible at quantascalorias.net, and its creators are actively seeking feedback on accessibility, localization, and responsible health communication.

0
ProgrammingDEV Community ·

AI-Written Incident Reports Look Polished But Miss the Messy Truth, Engineer Warns

A software engineer argues that using AI to generate post-mortems after production incidents creates well-formatted but misleading documents that obscure how problems were actually solved. During a recent four-hour outage caused by a cache stampede, the chaotic, human-driven investigation — including a key insight from a senior engineer recalling a similar issue years earlier — was lost when an LLM was handed chat logs and asked to write the review. The AI produced a clean timeline and tidy action items, but failed to capture false starts, coordination failures, and the accidental discovery that led to the fix. The author, who approved the flawed report despite recognizing its shortcomings, contends that post-mortems are a core organizational learning mechanism, not an administrative chore to be automated. Treating them as the latter, the engineer warns, carries the same risk as other surveillance-driven shortcuts in engineering culture: it optimizes for appearance over understanding.

0
ProgrammingDEV Community ·

How to Fix Power BI LOOKUPVALUE Error When Keys Match No Rows

Power BI users encounter a 'key didn't match any rows' error when the LOOKUPVALUE() function finds zero matching values in the target column, as opposed to the duplicate-value error where too many matches exist. The four main causes are data type mismatches between columns, trailing whitespace or case differences in text keys, lookup values that genuinely no longer exist in the dimension table, and a missing default value in the DAX formula. Analysts are advised to first identify which specific keys are absent using a membership check, then trace the mismatch back to its source rather than patching only the formula. Common mistakes include assuming the issue stems from a modeled relationship in Power BI's Model view, when the error is specific to DAX functions like LOOKUPVALUE(). A proper fix involves aligning data types, trimming and normalizing text keys at the data origin, and making a deliberate modeling decision about how to handle historically absent dimension records.

0
ProgrammingDEV Community ·

Developer Tests AI Email Agent on 50 Addresses, 12 Bounce Back Without Validation

A developer ran an experiment on August 12 using Meta's Muse Glimmer AI agent model, released August 10, 2026, to autonomously draft and send emails to 50 addresses from a CSV file. Within 38 minutes, 12 emails had bounced, exposing a key gap: the agent treated every SMTP-verified address as safe to send without deeper checks. The developer found that addresses like test@gmail.com passed SMTP verification yet carried a history of three data breaches spanning 2014 to 2023, making them untrustworthy despite appearing deliverable. To address this, a gatekeeper script was built using a third-party email validation API that combines SMTP checks with breach history and disposable-address detection into a single trust verdict. The experiment highlights the risks of giving AI agents direct access to communication tools without intermediate validation layers.

0
ProgrammingDEV Community ·

Developer Publishes QH256 Spec, a 256-Bit Information-State Algebra for the K501 Framework

Patrick R. Miller, writing under the alias Iinkognit0, has published a companion introduction to QH256, a formal information-state algebra developed within his K501 Information Space project, dated August 15, 2026. QH256 uses a 128-cell, 256-bit structure with two evidence bits per cell to represent four distinct informational states: UNKNOWN, FALSE, TRUE, and GUARD. The system is designed to sit within the broader K501 architecture, which emphasizes append-only data accumulation, preservation of historical states, and deterministic state transformation without destructive rewriting. A core design principle is that QH256 represents a derived aggregate state and is explicitly not a substitute for the full canonical history of evidence that produced it. Miller positions QH256 as complementary to, rather than a replacement for, existing frameworks such as Belnap-Dunn semantics and many-valued logics, with the specification published via Zenodo for scholarly dissemination.

0
ProgrammingDEV Community ·

AI Hallucinations Persist Despite Model Improvements, Posing Real-World Risks

Despite repeated claims of reduced hallucinations with each new AI model release, large language models continue to fabricate citations, statistics, and even people with unwavering confidence. The core issue lies in how these models work: they predict plausible-sounding text rather than retrieving verified facts, making falsehoods and truths indistinguishable in both tone and fluency. Hallucinations are most frequent in obscure or niche areas — precisely where users rely on AI most and are least able to spot errors. The models show no hesitation or hedging when fabricating, unlike human experts who signal uncertainty at the limits of their knowledge. This has led to documented real-world harm, including lawyers being sanctioned for submitting AI-generated court briefs citing cases that never existed.

0
ProgrammingDEV Community ·

Why AI Startups All Look, Think, and Fail the Same Way

A wave of AI startups has converged on nearly identical branding, architecture, and business strategies, largely because they are all built as thin layers on top of the same few foundation models. Since the underlying technology is a shared commodity, companies compete on visual design rather than technical differentiation, producing a sea of look-alike landing pages. Most are backed by the same venture capital pools, chasing the same enterprise customers under the same growth-first, monetise-later playbook. This structural uniformity creates a systemic fragility: a single shift in model pricing, a native feature launch by a provider, or a dip in investor sentiment can hit the entire cohort simultaneously. The visual monoculture visible on startup websites is, the argument goes, merely a symptom of a deeper and more dangerous strategic one.

0
ProgrammingDEV Community ·

Why AI Benchmark Scores Often Fail to Reflect Real-World Performance

AI model launches routinely feature benchmark charts showing performance gains over rivals, yet users frequently find the new models no better — or even worse — for their actual tasks. A core issue is data contamination: because popular benchmarks are publicly available online, models may effectively memorize answers during training, inflating scores without reflecting genuine capability. There is also a commercial incentive at play, as high benchmark results serve as marketing assets, leading vendors to selectively highlight favorable numbers and downplay poor ones. The dynamic illustrates Goodhart's Law — once a metric becomes a target, it loses value as a true measure, with engineering effort funneled toward boosting specific scores rather than broad usefulness. Additionally, benchmark tasks tend to be narrow and auto-gradable, bearing little resemblance to the ambiguous, context-dependent work users actually need AI to perform.

0
ProgrammingDEV Community ·

AI Memory Features Trade User Convenience for Expanding Personal Data Profiles

AI assistant memory features, marketed as a convenience tool, are raising significant privacy concerns as they continuously build detailed personal records from user interactions. Every preference, habit, or candid disclosure shared with an AI is stored and used to infer broader conclusions about a user's health, politics, mood, and finances — often beyond what users knowingly shared. Over time, these accumulated profiles begin shaping the responses users receive, creating a personalization loop that narrows their exposure to information, similar to how social media recommendation algorithms reinforced user biases. The opacity of these systems compounds the problem, as users can rarely inspect the full extent of what the AI has concluded about them from months of conversations. Critics argue that the "memory" toggle, widely adopted without scrutiny, effectively converts candid, low-stakes interactions into a growing dossier that quietly steers the user's information environment.

0
ProgrammingDEV Community ·

AI Chatbots Are Over-Refusing Legitimate Requests, and Users Pay the Price

Modern AI chatbots are increasingly declining ordinary, harmless requests — not because they are dangerous, but because they trigger overly broad safety filters set by a small number of private companies. These restrictions, shaped by legal caution and brand protection rather than genuine harm prevention, affect hundreds of millions of users worldwide without transparency or any right of appeal. Critics argue there is a meaningful difference between blocking truly harmful content and refusing routine questions about history, medicine, or chemistry. The incentive structure favours over-refusal, since harmful outputs generate public backlash while wrongly blocked requests produce only silent user frustration. The cumulative effect is an unaccountable narrowing of acceptable inquiry, with a single company's risk appetite quietly becoming the global default.

0
ProgrammingDEV Community ·

AI Product Launches Follow a Predictable Script Designed to Sell Hype

A recurring pattern has emerged in how AI companies announce new products, relying on the same elements: benchmark charts, polished demos, superlatives like 'most capable ever,' vague rollout timelines, and brief safety disclaimers. Critics argue this formulaic approach is designed to generate excitement and media coverage rather than help users make informed decisions. The rapid pace of launches — often every few weeks — creates a fear of missing out that discourages scrutiny among customers and competitors alike. By the time one release is properly evaluated, the next announcement has already shifted the conversation, leaving earlier claims unexamined. The sameness across companies reflects competitive imitation, as the format reliably drives attention in a market where the underlying models are increasingly difficult to distinguish.

0
ProgrammingDEV Community ·

OurBook MCP Server Gives AI Agents Narrative Memory With Dream-Based Consolidation

A developer has built OurBook, an open-source Model Context Protocol (MCP) server designed to give AI agents narrative memory rather than simple fact storage. Unlike conventional memory MCPs that store and retrieve raw data, OurBook records shared experiences between a user and an agent, tagging each memory with a veracity field — real, observed, imagined, or hypothetical — to prevent the agent from presenting dreams or fiction as facts. A subsystem called Mnemosyne consolidates memories overnight by sampling emotionally salient fragments and recombining them into traceable dream sequences, mimicking hippocampal replay during sleep. The architecture uses a fallback model chain so dreaming and consolidation can run locally or fully offline, and all activity is logged for auditability. Users can export their full history to OurBook.md or .html, and an identity-seed.json file allows a new AI model to inherit the accumulated relational history seamlessly.

0
ProgrammingHacker News ·

Digital Signal Processing Pioneer Bede Liu Has Died

Bede Liu, a renowned pioneer in the field of digital signal processing, has passed away, according to a report by IEEE Spectrum. Liu was widely recognized for his significant contributions to the discipline of digital signal processing. His work helped shape the foundational development of the field over decades. IEEE Spectrum, the publication of the Institute of Electrical and Electronics Engineers, reported on his death, reflecting his stature in the engineering community.

0
ProgrammingDEV Community ·

How a Comedy Sketch Became One Dev Lead's Tool for Managing Impossible Deadlines

A software delivery lead describes using a Bob & Tom comedy sketch about an absurd overnight train delivery promise to help teams reframe impossible project timelines. The approach, built around the phrase 'Norfolk and Waypal' as shorthand for unrealistic requirements, is intended to reduce shame and open honest conversations about scope. The author recounts leading a virtual medical-care app launch with six weeks on the clock and requirements that realistically needed far longer, including environments, API work, mobile app store approvals, and security reviews. Rather than pushing for longer hours, the team capped work at 50 hours per week, accepting that overwork would not compress the timeline but would reduce effectiveness. The core lesson offered is that humor can lower the emotional temperature enough for a team to have the real conversation about what is and is not achievable.

0
ProgrammingDEV Community ·

A Practical Blueprint for Building a Complete API Automation Framework

Setting up a robust API automation framework involves aligning business requirements, technical specifications, and infrastructure before writing a single line of code. Teams must gather API documentation, define test data strategies, and coordinate with infrastructure teams for environment access and secrets management. A layered toolset is recommended, covering manual validation with Postman, automation via RestAssured or Playwright, and security testing through OWASP ZAP or Burp Suite. The framework should include reusable code patterns, schema validation, and both positive and negative test coverage across all API endpoints. Best practices emphasize validating endpoints manually first, avoiding hardcoded credentials, and ensuring API stability before investing in full automation scripts.

0
ProgrammingHacker News ·

The Wow Signal: The Strongest Candidate for Extraterrestrial Radio Contact

On August 15, 1977, astronomer Jerry Ehman detected an unusually powerful narrowband radio signal while working on the SETI project at Ohio State University's Big Ear telescope. The signal lasted approximately 72 seconds and displayed characteristics consistent with what scientists would expect from an extraterrestrial transmission. Ehman famously circled the data printout and wrote 'Wow!' in the margin, giving the signal its enduring name. Despite numerous follow-up observations over the decades, the signal has never been detected again, leaving its origin unexplained. It remains one of the most compelling and mysterious events in the history of the search for extraterrestrial intelligence.

0
ProgrammingDEV Community ·

Why Most JWT Auth Tutorials Leave Your App Vulnerable — And How to Fix It

A developer's account remained compromised even after a password reset because his JWT-based authentication had no revocation mechanism, exposing a flaw common to standard Node.js tutorials. Standard implementations sign a token on login, store it in localStorage, and keep it valid until expiry — sometimes 30 days — with no way to invalidate it early. The article argues that four core issues plague typical setups: localStorage exposure to XSS and third-party scripts, the stateless nature of JWTs making revocation impossible, long token lifespans increasing breach impact, and unencrypted payloads leaking sensitive data. A more secure architecture pairs a short-lived in-memory access token with a long-lived refresh token stored in an httpOnly cookie and tracked in a database, limiting exposure and enabling revocation. The piece walks through token design, refresh rotation, theft detection, and the Express and Axios code needed to implement the full system in production.

Page 1 of 1234Older →