Why We Keep Building Someone Else's Platform: On Attribution, Extraction, and Developer Worth

I was debugging a production issue at 2 AM last week when it hit me. I was solving a problem that some developer at a FAANG company probably solved five years ago, documented in an internal wiki, and never shared. Meanwhile, I'd spend the next three hours researching, experimenting, and eventually arriving at the same solution—which I'd then publish on my blog where maybe 200 people would read it. The person whose internal documentation solved this first? They'd never get credit. Their company would.

This observation gnawed at me until I read something that reframed it entirely: a piece about how the Global North has systematized the extraction of intellectual work from everywhere else. It wasn't just about tech—it was about centuries of pattern. And suddenly I wasn't thinking about my 2 AM debugging session. I was thinking about why we accept this model at all.

The Gatekeeping Never Left Tech—It Just Wore Different Clothes

The original article walks through the history of scientific discovery in Latin America: brilliant researchers like Sergio Henrique Ferreira isolating molecules that became life-saving drugs, Carlos Chagas discovering an entire disease from a train car, Carlos Finlay identifying disease vectors years before Western medicine caught up. All of them invisible in the final history books. Credit went to whoever published it first in London or New York.

In tech, we've done the exact same thing. We've built a hierarchy where a tutorial published by a Stanford dropout goes viral and shapes industry practice, while equally rigorous technical writing from developers in Southeast Asia, Africa, or Latin America circulates in smaller circles. We've normalized this through conference speaking slots, GitHub stars, and who gets invited to speak at the fancy conferences.

I notice it every time someone posts a "revolutionary" framework or technique that solves something developers in other regions were already solving—but those solutions didn't get distribution. They didn't get the platform. The inequality isn't about talent or insight. It's about infrastructure and amplification.

What This Actually Looks Like in Our Industry

When I hire engineers or review code from developers across different regions, I see the same pattern the article describes. A developer in Islamabad writes production-grade infrastructure code. A developer in San Francisco writes a Medium post about "lessons learned" doing the same thing, and one gets picked up by algorithmic recommendation while the other remains invisible.

The gatekeeping in tech has layers:

• Distribution networks (which platforms amplify whose content)
• Credentialing theater (which universities and certificates "count")
• Conference lineups (who gets the stage and the visible authority)
• Hiring loops (who gets assumed competent vs. who has to prove it constantly)

What made the original article strike me was its refusal to call this accidental. This is engineered. We've built systems that extract value from the periphery and concentrate prestige at the center.

My Take: We Have More Power Than We Think

Here's where I disagree slightly with a purely extraction narrative: developers have more agency than scientists of past centuries. I can publish today. I can build and ship code without institutional permission. A well-built GitHub project doesn't require a prestigious sponsor to work.

But—and this is crucial—that access only matters if the infrastructure to be seen actually exists. And that infrastructure is still heavily weighted toward English, toward proximity to major tech hubs, toward people with the time and safety to contribute visibly.

What I'm doing differently: I'm intentionally amplifying developers from underrepresented regions when I see their work. I'm being explicit about attribution in my own writing. I'm pushing back when hiring teams dismiss candidates because they don't have the "right" school name or don't speak the exact dialect of tech English expected.

More practically: I'm documenting the problem-solving process itself, not just the solution. This shifts credit from "who published first" to "who actually understood the problem." It's a small shift, but it changes how work gets valued.

What I'm Actually Asking Myself

The original piece ends by arguing that AI democratization might finally break these gatekeeping patterns. I'm skeptical about that framing, but I'm genuinely uncertain. Does widespread access to AI tools actually redistribute power, or does it just make the extraction faster?

I don't have a clean answer. But I know that waiting for systems to fix themselves hasn't worked for centuries.

What I'm trying: being explicit about where ideas come from, citing the people whose actual code or thinking I'm building on, and creating space for developers from the Global South in every team I influence.

The question I keep wrestling with: Are you building platforms that concentrate visibility, or are you building infrastructure that distributes it? Because those are different problems, and the second one requires intention.

Source: This post was inspired by "The AI Era: Democratizing the Ivory Tower and Reclaiming the Latin American Mind" by Dev.to. Read the original article