NetBux All articles
Community & Digital Equity

Tech's Inclusion Problem Is Everyone's Problem — And It's Time to Fix It

NetBux
Tech's Inclusion Problem Is Everyone's Problem — And It's Time to Fix It

Photo: Evgeny2665, CC0, via Wikimedia Commons

Let's be honest about something: the technology sector has a habit of congratulating itself. We celebrate disruption, worship at the altar of innovation, and talk endlessly about changing the world. But when you look at who's actually in the room — who's writing the code, making the funding decisions, shaping the products — the picture is a lot narrower than the rhetoric suggests.

This is an opinion piece, so let me be direct: digital equity in the United States is not improving fast enough. And the open tech community, which prides itself on shared knowledge and collective progress, has a particular responsibility to do better.

Who Gets Left Out — and Why It Matters

According to the National Skills Coalition, roughly one-third of American workers lack the digital skills needed to participate fully in today's economy. That gap doesn't fall evenly. It hits Black and Latino communities harder. It hits rural Americans harder. It hits people with disabilities, older adults, and low-income households harder.

And it's not just about who can access the internet or use a smartphone. It's about who gets to build the technology the rest of us use. Women make up about 26% of computing-related jobs in the US, a figure that has barely moved in years. Black and Hispanic workers are significantly underrepresented across engineering, product, and leadership roles at major tech companies. The numbers are well-documented. The excuses are wearing thin.

Why does this matter beyond basic fairness? Because the people who build technology make choices — about what problems to solve, whose needs to prioritize, what assumptions to bake into algorithms. When those builders come from a narrow slice of society, the technology reflects that narrowness. We've seen this play out in facial recognition systems with higher error rates for darker skin tones. In health apps that didn't account for menstrual cycles for years. In voice assistants that struggled with non-American accents. These aren't abstract harms. They affect real people.

The Open Source Community Isn't Off the Hook

Some folks in open-source circles assume that because their work is free and publicly available, it's automatically more equitable. That's a comfortable story, but it's not quite true.

Open-source contribution has its own access barriers. You need time — something people working two jobs or managing caregiving responsibilities don't have in abundance. You need the confidence to submit a pull request to a project maintained by people who don't look like you. You need a computer capable of running a development environment, a reliable internet connection, and ideally some mentorship to get started.

Research consistently shows that open-source communities skew heavily male, heavily white, and heavily concentrated in wealthy countries and coastal US metros. The "anyone can contribute" promise is real in theory. In practice, the path is a lot smoother for some people than others.

What Platforms Can Actually Do

This is where I want to get specific, because vague calls for "more diversity" don't move anything. Platforms, companies, and community organizers have concrete levers to pull.

Lower the floor for first-time contributors. Projects should have genuine "good first issue" tags — not just issues labeled that way but never triaged. Maintainers who respond warmly and quickly to first contributions create a very different culture than those who ghost or gatekeep.

Fund underrepresented contributors directly. Organizations like Open Source Collective and Code for America are doing important work, but they need more resources. Tech companies that benefit enormously from open-source infrastructure should be writing bigger checks to programs that bring underrepresented developers into that ecosystem.

Design for accessibility from the start. Accessibility isn't a feature you bolt on at the end of a product cycle. It's a design philosophy. Tools, platforms, and APIs should be built with screen readers, keyboard navigation, and cognitive accessibility in mind from day one.

Show your demographic data — and be honest about it. Companies that publish detailed, honest breakdowns of their workforce composition create accountability. Those that bury the numbers or only report favorable slices are telling you something about their priorities.

What Individuals Can Do Right Now

It's easy to point at platforms and companies and say "fix it." But collective progress — which is genuinely what this community is about — requires individual action too.

If you're a senior developer, mentor someone who doesn't have the same background you do. Not as a charity project, but as a genuine professional relationship. If you're running a meetup or a tech event, look at your speaker lineup. If it's all the same demographic, that's a choice you made, even if passively.

If you're hiring, examine your job descriptions. Requirements like "culture fit" are often proxies for sameness. Unpaid internships filter out candidates who can't afford to work for free. Requiring a four-year degree for roles that don't genuinely need one cuts out people who built their skills through community colleges, bootcamps, or self-teaching — often the most resilient and motivated learners you'll find.

And if you have a platform — a newsletter, a podcast, a popular GitHub repo — use it to amplify underrepresented voices. Not tokenistically. Genuinely.

The Stakes Are High

America is in the middle of a massive digital transformation. Artificial intelligence is reshaping industries. Broadband infrastructure is finally being expanded to rural communities through federal investment. Remote work has opened up tech careers to people who couldn't afford to live in San Francisco or Seattle.

This is a genuine window of opportunity. But windows close. If the communities building the next generation of technology don't actively work to include the people who've historically been excluded, we'll end up with the same skewed outcomes dressed up in shinier packaging.

At NetBux, we believe that open tech and shared knowledge aren't just branding — they're commitments. Commitments that only mean something if they extend to everyone. The developers in rural Appalachia. The self-taught coders in South Chicago. The women returning to the workforce after raising kids. The immigrants and first-generation college students who bring perspectives that make technology smarter, more resilient, and more human.

Collective progress isn't a metaphor. It's a practice. And right now, we're not practicing it nearly well enough.

All Articles

Related Articles

From Passion Projects to Paychecks: The New Business of Open Source

From Passion Projects to Paychecks: The New Business of Open Source