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

推荐订阅源

博客园 - 叶小钗
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Microsoft Security Blog
Microsoft Security Blog
罗磊的独立博客
大猫的无限游戏
大猫的无限游戏
美团技术团队
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
aimingoo的专栏
aimingoo的专栏
腾讯CDC
WordPress大学
WordPress大学
Apple Machine Learning Research
Apple Machine Learning Research
F
Fortinet All Blogs
G
Google Developers Blog
MongoDB | Blog
MongoDB | Blog
Microsoft Azure Blog
Microsoft Azure Blog
小众软件
小众软件
Engineering at Meta
Engineering at Meta
博客园_首页
B
Blog RSS Feed
D
Docker
M
MIT News - Artificial intelligence
爱范儿
爱范儿
I
InfoQ

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
The Number Your Accuracy Score Is Not Telling You: What I...
Sanskriti · 2026-06-03 · via DEV Community

This is a submission for the GitHub Finish-Up-A-Thon Challenge

What I Built

In 2017 I trained a charity donor classifier for a Udacity machine learning nanodegree project. The task was to predict whether someone earns more than $50k per year as a proxy for donation likelihood for a fictional charity called CharityML. Gradient Boosting won the model comparison at 86.78% accuracy and an F-score of 0.7469. I submitted it, got my grade, and filed the notebook away.

Coming back in 2026, I did not just fix the code. I audited what the model actually learned. The answer was uncomfortable.

Demo

Live demo: https://sanskriti1991.github.io/machineLearningProjects/finding_donors/

GitHub repo: https://github.com/sanskriti1991/machineLearningProjects/tree/master/finding_donors

The demo lets you input census features and see how the model predicts donation likelihood. It shows a fairness warning for demographic groups with known prediction disparities and charts the prediction rates, false positive rates, and false negative rates across all demographic groups.

Prediction form showing age slider, education, occupation, gender and race inputs

The Comeback Story

Before: a notebook that could not run on any modern setup

Opening the notebook in VS Code on Python 3.13 with current sklearn revealed three immediate problems.

The sklearn imports had not kept up with eight years of library changes:

# 2017 — no longer works
from sklearn.cross_validation import train_test_split
from sklearn.grid_search import GridSearchCV

Enter fullscreen mode Exit fullscreen mode

The print statements were Python 2 syntax throughout. And the visualization helper file had an integer division bug where j/3 returns a float in Python 3, breaking array indexing entirely. One character fix changed j/3 to j//3. The notebook had silently needed it for eight years.

After: a running notebook with a fairness audit

Once the code ran, I started looking at the dataset more carefully. The UCI Adult Income dataset extracted from the 1994 US Census had appeared in hundreds of published research papers by 2021, spanning AI fairness, privacy preservation, and model debugging. UC Berkeley researchers published "Retiring Adult" at NeurIPS 2021 calling for it to be retired.

Their finding: the $50k income threshold used as the positive class label was the 76th income percentile overall in 1994, but the 88th percentile for Black Americans and the 89th percentile for women.

The model did not learn who donates. It learned who 1994 America paid well.

The fairness audit made that concrete:

  • Asian-Pac-Islander males predicted as likely donors: 32%
  • White males: 26%
  • Black females: 4%
  • American Indian females: nearly 0%

86.78% overall accuracy. Completely silent on all of the above.

My Experience with GitHub Copilot

Working with Copilot on this project was not a smooth straight line. It was honestly more like a collaboration that required patience on both sides.

The rate limit reality

I am on the free Copilot tier. Partway through the session, after several back and forth prompts fixing the deprecated imports and print statements, Copilot hit its rate limit and went quiet. I had to wait for it to reset before continuing. That could have been the moment I gave up. It wasn't. I kept the notebook open, documented what had been fixed so far, and came back when the quota reset.

Learning to prompt better

My first prompts were too broad. Asking Copilot to fix the entire notebook at once produced suggestions it could not apply directly to notebook cells in the browser environment. I had to adjust, breaking the task into smaller pieces and being more specific about what I needed. That back and forth was frustrating at first but it forced me to understand the changes rather than just accepting them blindly.

Where Copilot genuinely delivered

Once I found the right prompt style the three moments that mattered most were clear.

First, identifying the deprecated sklearn imports and explaining exactly why each module had moved. Old line, new line, reason. Clear and immediately useful.

Second, catching the integer division bug in visuals.py where j/3 silently breaks in Python 3. I would have spent a long time hunting that one down without Copilot pointing at the exact line.

Third, generating the full fairness audit from a single inline comment. That was the most impressive moment. One descriptive comment and Copilot produced working code that reconstructed demographic groups from one-hot encoded columns, calculated prediction rates and error rates by group, and saved the charts. It then summarized the findings in plain English:

"The model appears to have learned patterns reflecting 1994 wage inequality rather than actual donation likelihood. This suggests that systemic biases in income distribution at the time are influencing the model's predictions."

That is the sentence I should have written in 2017. Now I have.


Why this dataset was called for retirement (UC Berkeley, NeurIPS 2021): https://arxiv.org/abs/2108.04884