惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Vercel News
Vercel News
SecWiki News
SecWiki News
WordPress大学
WordPress大学
小众软件
小众软件
博客园 - 司徒正美
酷 壳 – CoolShell
酷 壳 – CoolShell
V
Visual Studio Blog
Y
Y Combinator Blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
云风的 BLOG
云风的 BLOG
MyScale Blog
MyScale Blog
K
Kaspersky official blog
T
The Exploit Database - CXSecurity.com
腾讯CDC
Scott Helme
Scott Helme
I
InfoQ
Cyberwarzone
Cyberwarzone
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Security Latest
Security Latest
The Register - Security
The Register - Security
Project Zero
Project Zero
F
Fortinet All Blogs
C
CERT Recently Published Vulnerability Notes
A
Arctic Wolf
C
Cisco Blogs
L
LINUX DO - 热门话题
P
Privacy International News Feed
IT之家
IT之家
U
Unit 42
P
Privacy & Cybersecurity Law Blog
H
Help Net Security
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
C
Cyber Attacks, Cyber Crime and Cyber Security
P
Palo Alto Networks Blog
F
Full Disclosure
宝玉的分享
宝玉的分享
Simon Willison's Weblog
Simon Willison's Weblog
L
Lohrmann on Cybersecurity
Google DeepMind News
Google DeepMind News
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
H
Hacker News: Front Page
Know Your Adversary
Know Your Adversary
PCI Perspectives
PCI Perspectives
Hugging Face - Blog
Hugging Face - Blog
AWS News Blog
AWS News Blog
MongoDB | Blog
MongoDB | Blog
S
Schneier on Security
Recent Announcements
Recent Announcements
Forbes - Security
Forbes - Security
Cisco Talos Blog
Cisco Talos Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
Why I put a 4-qubit circuit inside a brain tumor classifier
Anubhav Verma · 2026-06-21 · via DEV Community

A few months ago I would have told you quantum machine learning was mostly hype dressed up in cool-sounding words — "superposition," "entanglement," "quantum advantage" — thrown around papers that never quite show you the number that matters. Then I built one of these systems myself, for something that actually has stakes: classifying brain tumors from MRI scans. And I came out the other side with a more interesting opinion than "hype" or "revolution." It's somewhere in between, and the in-between is where the actual engineering lives.

The setup: a classifier that already worked fine

I didn't start from scratch. The backbone of the system is DenseNet121, a convolutional architecture that's been doing solid work on medical imaging for years. Trained on MRI slices, a plain DenseNet121 classifier already gets you a respectable accuracy on tumor classification. If your only goal is "ship something that works," you could stop there and nobody would blame you.
So why didn't I stop there?
Because "works" and "trustworthy enough to sit next to a radiologist" are different bars. Medical imaging is one of the few domains where a model being slightly better isn't really the point — the point is whether you can explain why it made a call, and whether that explanation would survive a doctor asking "wait, why?" That question is what pulled me toward two very different ideas at once: quantum circuits and explainability, bolted onto the same model.

Where the qubits come in

The quantum part isn't replacing the neural network — that's a common misconception about hybrid quantum-classical models, and it's worth being blunt about. DenseNet121 still does the heavy lifting: extracting features from the MRI images, learning what textures and shapes correlate with tumor types. What I added on top is a 4-qubit variational quantum circuit, built with PennyLane, sitting at the tail end of the pipeline where the classical network would normally just feed straight into a final classification layer.
A variational quantum circuit is, at a practical level, a small set of parameterized quantum gates whose parameters get trained the same way a classical layer's weights get trained — through gradient descent, just computed via a different mechanism (parameter-shift rules instead of standard backprop). The promise is that the quantum circuit can represent certain non-linear feature interactions more efficiently than a classical layer of comparable size, because superposition lets it explore a larger effective feature space with fewer parameters.
In this project, that promise showed up as a real, measurable gain over the classical-only baseline. Swapping the final classical layer for the 4-qubit circuit pushed accuracy up by around six percentage points. That's not a "we ran it once and got lucky" number — it held up across the held-out test set. But I want to be honest about what that gain actually represents, because "quantum gives you free accuracy" is the wrong takeaway.

The gain is real, but it's not magic

What the quantum layer is really doing here is acting as a different kind of non-linear transformation on the features DenseNet121 has already extracted — one that's harder to replicate exactly with a classical layer of the same parameter count. Whether that's because of genuine quantum effects or just a different inductive bias that happens to fit this dataset well is an open and genuinely debated question in the QML literature, and I don't think it's fully settled even by people far more qualified than me. What I can say with confidence is: on this dataset, with this architecture, the hybrid model classified more tumors correctly than the classical-only one did, consistently.
The honest framing I'd give anyone asking "should I add a quantum layer to my model" is: it's a tool worth testing when your classical model has plateaued and you have a small number of features feeding into a final decision layer — 4 to 8 qubits is the realistic, simulable range right now. It is not a tool for squeezing performance out of a model that's already well-fit, and it is absolutely not free — every quantum circuit you simulate classically costs you exponentially more compute as qubit count grows.

Trusting the model: Grad-CAM and SHAP, together

The accuracy gain was the smaller part of why I built this. The bigger part was explainability, because a 6% lift means nothing in a clinical context if you can't show why the model is making its decisions.
I used two explainability techniques side by side, deliberately, because they answer different questions:
Grad-CAM answers "where in the image was the model looking?" It produces a heatmap over the MRI slice, highlighting the regions that most influenced the classification. For a tumor classifier, this is the sanity check a radiologist would actually want — does the hot region in the heatmap correspond to the tumor, or is the model fixating on some artifact in the corner of the scan?
SHAP answers a different question: "of the features the model extracted, which ones mattered most for this specific prediction, and in which direction?" Where Grad-CAM is spatial, SHAP is attributional — it decomposes the prediction into per-feature contributions, which is useful for catching cases where the model's spatial attention looks fine but its actual decision logic is leaning on something subtle and wrong.
Running both gave me a much more complete picture than either alone would have. There were a handful of cases where Grad-CAM's heatmap looked perfectly reasonable — centered right on the tumor — but SHAP revealed the model was still weighting some unrelated texture feature more heavily than it should have. Without the second lens, I'd have shipped that case as "explained" when it wasn't really.

Noise, and why NISQ matters more than people think

The last piece — and the part that gets skipped in a lot of QML write-ups — is noise evaluation under NISQ (Noisy Intermediate-Scale Quantum) conditions. Right now, every real quantum computer is noisy. Gates have error rates, qubits decohere, and a circuit that works beautifully in a noiseless simulation can degrade meaningfully once you account for realistic hardware noise.
I didn't just train the model on a clean simulator and call it done — I evaluated how the 4-qubit circuit's performance held up under simulated NISQ noise conditions, because that's the actual environment any near-term quantum hardware will run in. This matters for one practical reason: if you're going to claim a quantum-enhanced model is viable, you have to show it's still better than the classical baseline after accounting for the noise you'd see on real hardware, not just in the idealized simulator where every gate is perfect.

Where I landed

If you're considering a hybrid quantum-classical approach for your own project, here's the honest summary: it's a legitimate technique, not a buzzword, but it's a narrow tool. It earns its place when you have a small, well-defined final decision layer, when you've already squeezed what you can out of the classical architecture, and when you're willing to do the unglamorous work of explainability and noise evaluation rather than just reporting one accuracy number and calling it a day.
The six points of accuracy were nice. The two explainability methods agreeing with each other — most of the time — was the part that actually made me trust the system.