SShortSingh.

Programming

0
ProgrammingDEV Community ·

RecallOps Uses Persistent Memory to Help Engineers Learn from Past Incidents

RecallOps is a tool designed to improve engineering incident response by storing and retrieving historical incident data as reusable memory. When an engineer investigates an active incident, the system searches for relevant past experiences to provide useful context rather than replacing human judgment. The platform's dashboard consolidates incident viewing, memory-based investigation, and outcome recording in one place. Engineers can log whether a fix succeeded or failed, with both outcomes feeding back into the system's knowledge base for future use. Built with Python and integrated with tools like Sentry and Hindsight, RecallOps aims to make engineering knowledge increasingly valuable over time.

0
ProgrammingDEV Community ·

Bitget DeFi Protocol Rated Medium-High Risk With $5.9B TVL Under Scrutiny

A DeFi security assessment dated September 28, 2026, evaluated Bitget, a multi-chain liquidity and derivatives platform currently holding $5.92 billion in total value locked across Ethereum and Layer 2 networks. The protocol received an overall risk rating of 6.8 out of 10, driven by rapid TVL growth of 3.2 times since early 2023 and heavy concentration on L2 chains, which now account for 68% of assets. Auditors identified cross-chain bridge exposure as the most critical vulnerability, with roughly $1.07 billion at risk from potential exploits on Arbitrum and Optimism bridges. Oracle dependency on Chainlink and Pyth also raised concerns, as both feeds share underlying data providers, creating a single point of failure that could affect up to $450 million in leveraged positions. Additional risks include flash-loan-based liquidity drains and governance token mechanics that could be exploited to manipulate on-chain voting outcomes.

0
ProgrammingDEV Community ·

Address Space Bug Silently Broke 70% of Mailbox Creation for Weeks

A software engineer discovered that a disposable email address generator had quietly been failing for weeks due to address space exhaustion, affecting the majority of registered users. The system used a human-readable adjective-noun-number format with only 36,000 possible combinations, and by the time the issue was caught, 33,590 of those addresses were already taken. With 93% occupancy, the five-retry creation logic was failing roughly 70% of the time, yet no monitoring tool flagged the problem. Misleadingly, frontend error tracking recorded only 18 failures over six weeks because the error event was wired to just a subset of user paths, masking hundreds of actual API failures. The incident highlights how combinatorial exhaustion bugs can remain invisible until they cause near-total service failure, with no gradual degradation to trigger alerts.

0
ProgrammingHacker News ·

MongoDB CEO Quits to Join Meta, Shares Tumble 20%

MongoDB's CEO Dev Ittycheria has resigned with immediate effect to take up a leadership role overseeing Meta's enterprise platform. The sudden departure caught investors off guard, triggering a sharp 20% decline in MongoDB's stock price. The company has not yet announced a permanent successor to lead the database software firm. Ittycheria's move to Meta signals the social media giant's growing focus on building out its enterprise infrastructure capabilities.

0
ProgrammingDEV Community ·

Developer Launches Backkit, a Customizable CLI Tool for Scaffolding Node.js Backends

A developer has released Backkit, an open-source interactive command-line tool designed to automate the repetitive setup process for Node.js backend projects. Unlike fixed boilerplates, Backkit lets users choose their preferred stack by selecting from options including TypeScript or JavaScript, Express or Fastify, PostgreSQL or MongoDB, and various ORM and authentication configurations. The tool is available without a global install and can be run directly via npx, after which it guides users through an interactive setup wizard. Once configuration choices are made, Backkit generates the project structure, configures dependencies, and produces a ready-to-run development environment tailored to the selected stack. The project was motivated by the developer's repeated experience of spending significant time on boilerplate setup before beginning actual application logic across multiple Node.js projects.

0
ProgrammingDEV Community ·

Half of AI-Assisted Pull Requests Merged With No Human Review, Data Shows

A design engineer analyzed 1,239 pull requests merged across 49 repositories over four weeks in mid-2026, finding that 90.7% were AI-assisted and 50.6% received no review from any human account. While org-level dashboards showed improving metrics — a median of two comments per PR and fewer with zero comments — those figures included bot-generated reviews, which accounted for 635 of 898 reviews in the final week alone. When bot activity was stripped out, the share of pull requests lacking human review actually rose from 47.7% in July to 61.6% in the most recent week. The author argues that engineering teams have scaled code generation with AI but have not scaled genuine human oversight to match. He cautions that the findings come from a single organization and should be treated as indicative of a pattern rather than a universal benchmark.

0
ProgrammingHacker News ·

Lessons from Heraldry and Japanese Mon for Designing Visual-Identity Systems

A blog post published on benovermyer.com explores what traditional heraldry and Japanese mon (family crests) can teach designers about building visual-identity generators. The piece draws comparisons between Western heraldic traditions and Japanese mon design principles. The author examines the structural and symbolic rules underlying both systems as potential frameworks for automated or algorithmic identity creation. The article was shared on Hacker News, where it received 6 points at the time of aggregation.

0
ProgrammingDEV Community ·

DEV Community Members Share Weekly Goals, Projects, and Event Plans in Thread #198

DEV Community's recurring weekly goals thread, now in its 198th edition, invited developers to share what they are building, learning, and attending that week. Participants listed objectives ranging from job searching and networking to working on side projects and learning GitHub Copilot. Several community events were on the agenda, including Virtual Coffee on Thursdays and a Dallas Software Developers meetup. One contributor also prepared for an art show, facing a last-minute printer ink issue that was resolved by printing photos at Walgreens instead. The thread serves as a peer accountability space where members also report back on which goals they completed or missed.

0
ProgrammingDEV Community ·

Hindsight Tool Uses 'Failure DNA' to Spot Recurring Patterns in Past Incidents

A developer has built a tool called Hindsight that treats historical software incidents as engineering memory rather than isolated tickets. The tool introduces the concept of 'Failure DNA,' which identifies recurring root-cause patterns shared across multiple past incidents. Hindsight stores incidents in a SQLite database and uses a pattern library to track how often each root cause appears and which modules it affects. When a new issue is reported, the tool applies TF-IDF vectorization and cosine similarity to match it against historical incidents and surface the underlying failure pattern. The goal is not merely to find a similar old ticket but to help developers recognize repeated systemic failures before they escalate further.

0
ProgrammingDEV Community ·

Why AI Governance Belongs in Your Gateway, Not Your Policy Docs

Most teams enforce AI governance at the application level, leading to inconsistent PII redaction, fragmented logs, and untracked provider keys across services. This fragmented approach fails to provide a unified, auditable record of every model call — a gap that widens as organizations deploy more LLM-powered features and autonomous agents. An AI gateway addresses this by sitting between all applications and model providers, enforcing policies and logging every request in one place regardless of which team or SDK originated it. Developers can redirect existing OpenAI-compatible clients to a gateway with minimal code changes, while routing, credentials, and compliance rules are managed centrally. Centralizing governance as infrastructure — rather than per-app code — makes it possible to answer cross-cutting audit questions and enforce consistent controls at scale.

0
ProgrammingDEV Community ·

ISO 42001 Explained: What AI Governance Standard Demands from Engineering Teams

ISO/IEC 42001, published by ISO in December 2023, is a voluntary, certifiable international standard for managing AI systems within organizations. Unlike the EU AI Act, which is law with penalties, or SOC 2, which attests to security controls, ISO 42001 focuses on whether a company's AI governance processes are sound. Certification occurs in two stages: a document review of policies and risk registers, followed by an audit where teams must demonstrate controls actually operated as described. For engineering teams, the standard requires traceable evidence across the AI lifecycle, including data sourcing, impact assessments, and supplier responsibilities. Adoption is still early globally, but AI vendors selling to enterprises are already encountering it in security questionnaires, making early familiarity worthwhile.

0
ProgrammingDEV Community ·

Developer Builds AI Support Agent With Persistent Customer Memory

A developer has built a customer support agent that uses persistent memory to retain context from previous interactions, eliminating the need for customers to repeat themselves. The system combines a React frontend, a FastAPI backend, the Groq language model, and a memory layer called Hindsight to deliver context-aware responses. When a returning customer sends a vague follow-up message, the agent retrieves relevant past interaction data before generating its reply. The developer added a Memory ON/OFF toggle to the interface to clearly demonstrate the difference between stateless and memory-enabled responses. The project highlights how integrating structured memory retrieval into an AI agent's reasoning workflow can meaningfully improve support experiences.

0
ProgrammingDEV Community ·

Why Google's AI Overviews Sometimes Invent Answers Instead of Finding Them

A developer searching for a nine-word basketball meme phrase received an AI-generated response consoling him over a romantic breakup that never happened, highlighting a structural flaw in AI-powered search. The phenomenon, known as AI hallucination, occurs because large language models predict statistically probable word sequences rather than verifying factual accuracy before responding. Google integrated its AI Overviews feature into its main search results in 2024, placing generated summaries above traditional links where they attract the most user clicks. Researchers distinguish two hallucination types: intrinsic, where the model contradicts its own retrieved context, and extrinsic, where it adds information absent from any source. For developers, the risk is practical — an AI-invented API flag or library behavior can produce code that compiles but breaks in production.

0
ProgrammingDEV Community ·

Why a Passing Test Does Not Always Mean Your Code Is Truly Verified

A passing test confirms that a specific scenario produced the expected result, but it does not necessarily prove that the right behaviour was tested or that critical user flows were covered. This distinction became more apparent when examining AI-assisted testing tools, where tests can be generated quickly but may have weak assertions or inadequate test data. Platforms like X360 AI Tech address this by linking requirements, test coverage, execution, and results together rather than relying solely on a pass/fail status. This approach shifts the key question from whether a test passed to what behaviour the test actually validated. As AI makes test creation easier, understanding what each passing test genuinely proves is becoming the more challenging and important skill for developers.

0
ProgrammingDEV Community ·

Dev builds browser-based 3D RTS in plain JavaScript, shares key lessons learned

A solo developer released Singularity Rush, a free browser-based real-time strategy game built with roughly 6,700 lines of plain JavaScript and three.js, using no framework or bundler. The game simulates four AI labs competing to train an advanced model, with units mining data, generating compute, and sabotaging rivals. The developer kept the game simulation entirely separate from the rendering layer, enabling automated AI-vs-AI testing in CI and deterministic replays via a seeded random number generator. A post-launch surprise revealed that CDN caching overrode origin headers, causing mismatched JavaScript module versions for returning players, which was fixed by hashing filenames and using immutable URLs in production. The developer noted that while the no-build-step approach worked well during development, production deployment required additional tooling to handle caching and asset versioning reliably.

0
ProgrammingDEV Community ·

How to Build a Fully Private Local AI Stack Using Ollama, LM Studio and Continue

Developers can now run capable AI models entirely on local hardware using tools like Ollama, LM Studio, and the Continue extension for VS Code, eliminating recurring API costs. Advanced quantization formats such as GGUF, EXL2, and AWQ make it possible to deploy large language models on consumer-grade machines including Apple Silicon Macs and Linux servers. Ollama serves as a lightweight background daemon suited for automation, while LM Studio offers a desktop GUI for interactive model testing and hardware monitoring. Together, these tools support OpenAI-compatible API endpoints, enabling private RAG pipelines, secure enterprise workflows, and local coding assistants. The author recommends running both tools in parallel and routing prompts through IDE agents like Continue to replicate cloud-based AI capabilities without sending data to external servers.

0
ProgrammingDEV Community ·

Why sched_yield() Quietly Destroys CPU Cache Performance in Linux

Calling sched_yield() in Linux triggers a full kernel context switch rather than a lightweight wait, causing hardware registers to be saved, TLB entries to be flushed, and L1/L2 caches to be overwritten by the incoming thread. This process, managed by the Completely Fair Scheduler or EEVDF, places the yielding thread back on the runqueue with no guarantee of a timely or controlled return. The cache and pipeline disruption is especially damaging in high-throughput systems like low-latency trading engines or actor-framework thread pools, where sub-microsecond timing is critical. Developers often treat sched_yield() as a harmless scheduling courtesy, but under load it introduces significant tail latency across NUMA domains. Experts recommend replacing sched_yield() with deterministic hardware backoff strategies or proper kernel sleeping primitives to preserve execution efficiency.

0
ProgrammingDEV Community ·

Three AI Models Score Perfectly on Small C++ Bug Detection Benchmark

A C++ learner created a three-task benchmark on Kaggle to evaluate how well AI models detect common logical errors in code, as part of the DEV × Kaggle Benchmarking Challenge. The benchmark tested Qwen 3 Coder 480B, GPT-5.4 mini, and Gemini 3.7 Flash on tasks involving incorrect variable usage, off-by-one errors, and wrong array indexing. All three models achieved a perfect score of 100, successfully completing all nine model-task evaluations. The author acknowledges the benchmark is limited in scope and does not reflect model performance on complex codebases or real-world debugging scenarios. Future iterations are planned to include harder challenges such as pointer bugs, nested loops, and edge cases.

← NewerPage 840 of 3172Older →