Browser-Based Drug Interaction Tool Uses WebGPU to Keep Medical Queries Private

·1 views

A new developer tutorial demonstrates how to build a drug interaction checker that runs entirely within the user's browser, eliminating the need to send sensitive medical data to remote servers. The tool uses WebLLM and WebGPU to execute large language models such as Llama-3 or Mistral locally, leveraging the device's own GPU for processing. Built with React, TypeScript, and Vite, the application streams AI-generated responses in real time while ensuring complete on-device data residency. WebGPU enables low-level browser access to local graphics hardware, making it possible to run models typically requiring expensive server-side infrastructure. The project is framed as a privacy-first approach to medical AI, where no user input ever leaves the device.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Developer Ditches OpenSpec for AIDLC Workflow to Fix AI-Generated Code Quality

A software team lead spent over a month overhauling his team's AI coding workflow after noticing that while development speed had improved over six months, code quality remained poor and bug-fixing often took far longer than initial development. The team had been using Spec Driven Development (SDD) frameworks like OpenSpec, but found these tools difficult to standardize across a multi-team, long-running project. Complex commands and inconsistent adoption led some developers to abandon the workflow entirely and revert to unstructured 'vibe coding.' The lead replaced OpenSpec with a new approach called AIDLC, which incorporates a more detailed software development process and stronger team collaboration practices. According to the author, the switch resulted in a significant improvement in code quality across the team.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Dependency-Driven Structure Can Improve Game Wiki Troubleshooting Guides

A developer essay on DEV Community proposes a structured documentation model for game wiki guides, using the business simulation game Big Ambitions as a reference case. The model suggests organizing guides around explicit dependency relationships, where each prerequisite is described by its condition, its connection to other workflow elements, what readers can observe, and where to go next if something is missing. The author recommends dividing troubleshooting pages into sections with distinct responsibilities, such as summary, prerequisites, procedure, verification, and diagnostics, so readers can navigate directly to what they need. A dedicated verification section is emphasized to define what success looks like, rather than leaving outcomes ambiguous after a procedure ends. The piece also advocates storing version context and source evidence alongside factual claims, giving editors a clear way to maintain accuracy as game content changes over time.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Agent hook scripts fail open by default, posing silent security risks

Agent-CLI hooks, small programs that run before or after tool calls in AI coding harnesses like Claude Code, default to a fail-open state when they crash or return malformed output. This means a hook that throws an exception or receives unparsable input may silently allow a tool call to proceed rather than blocking it. The author of Handrail, an open-source hook pack, argues the fix must be structural: a top-level error trap that routes any uncaught failure to an explicit deny decision. The recommended pattern uses a narrow allow-list so that only known-safe cases produce an allow response, with everything else — including unknown or unparseable inputs — defaulting to deny. The Handrail toolkit, available under the MIT license on GitHub, packages this fail-closed design along with a fixture test suite and installer for Claude Code settings.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why Engineering Leads Should Never Write Code, According to One Developer

Software engineer Anton, who works primarily with PHP/Symfony and Go, argues that a technical lead's role should be strictly limited to preparing task facts, handing over work, and accepting results — never writing code directly. His workflow caps concurrent executors at three: two on main work and one on fixes, deliberately avoiding fan-out to prevent file conflicts and limit bottlenecks. According to Anton, the moment a lead starts coding, the critical fact-preparation step breaks down, making subsequent task batches more costly than any time saved. Each task must be handed to an executor as a complete, self-contained message requiring no further reading or clarification. After a set of tasks closes, a structured audit maps every original requirement to what was done and what proof exists, flagging any logic added outside the original statement.

0 comments Read more at DEV Community