Joy Buolamwini, 2016

“Who codes matters, how we code matters, and why we code matters.”

Buolamwini connected failures in commercial facial analysis to the narrow data and priorities used to build the systems, naming the resulting perspective the coded gaze. Reading Joy Buolamwini in the setting of “How I'm Fighting Bias in Algorithms” changes how the quotation lands. The year 2016 identifies the documented source, while April 15 is only this series' calendar position. That distinction protects Joy Buolamwini's words from a familiar problem: a compact sentence can travel farther than the reasoning that supported it. The original audience faced particular tools, constraints, and expectations; later readers bring different ones. Returning to “How I'm Fighting Bias in Algorithms” therefore does more than verify authorship. It clarifies the problem under discussion, shows what the speaker actually claimed, and marks where modern interpretation begins.

The people, methods, and purposes behind a system affect what it recognizes, whom it serves, and which failures receive attention. For a present-day team, Joy Buolamwini's idea becomes useful when it changes a decision instead of decorating a slide. A reviewer might use it to question an interface, architecture, dataset, workflow, or governance rule. The next step is to name the desired outcome, identify the people who experience the system, and choose evidence that could disprove the team's preferred story. This approach treats “How I'm Fighting Bias in Algorithms” as an argument to examine rather than authority to borrow. It also turns a memorable line into a practical test: what would builders do differently if they took its central insight seriously?

Representation on a development team is essential but not sufficient; testing, governance, affected-community power, and enforceable limits also matter. That qualification keeps Joy Buolamwini's sentence from becoming a universal slogan. Technical results live inside organizations, markets, laws, and communities, where a narrow benchmark rarely settles the whole question. A responsible reading of “How I'm Fighting Bias in Algorithms” makes assumptions visible, records tradeoffs, and asks who gains convenience and who inherits risk. It also leaves room for contrary evidence and affected people to change the conclusion. Preserving limits is not hostility to innovation; it connects ambition to accountability and makes correction possible before an elegant idea hardens into an expensive or harmful system.

Biometric systems and generative models continue to expose uneven performance and contested uses across race, gender, disability, and culture. The enduring value of Joy Buolamwini's quotation is therefore a method, not a formula. Individuals can use it to sharpen the next question, while organizations can use it to assign ownership, improve measurement, and explain why a design deserves trust. The strongest modern application of “How I'm Fighting Bias in Algorithms” combines historical accuracy with present evidence: understand the source, test the claim in its new environment, disclose important limits, and revise the implementation when real conditions disagree. Admiration for a famous technologist is optional; what matters is whether the idea helps people make technology more understandable, dependable, useful, and answerable to those it affects.