That's Exactly the Problem
This is a submission for the 2026 WeCoded Challenge: Echoes of Experience
The first time I walked into a university computer lab in Ghana, I didn't count the room.
That's the point.
I walked in, found a seat, opened my laptop, and got to work. I didn't calculate my odds. I didn't wonder if I belonged. I didn't brace for anything. The room was full of people who looked like me, spoke like me, had been told — implicitly, repeatedly, since childhood — that a future in technology was a reasonable thing for someone like me to want.
I had no idea, at the time, that this ease was a privilege. I thought it was just Tuesday.
It took watching my female classmates navigate the same room — the same lectures, the same group projects, the same career fairs — to understand that we were not having the same experience at all.
What I Started Noticing
Out of thirty-one students in my first Introduction to Programming class, four were women. I didn't notice that either, at first. It just seemed like the natural shape of things.
But then I started paying attention.
I noticed that when a woman answered a question correctly, there was sometimes a half-second pause before the response — a beat of mild surprise that was never there when I answered. I noticed that in group projects, the unspoken assumption was that the women would handle documentation and presentation — the "softer" edges of the work — and that nobody had decided this consciously. It had simply settled that way, like sediment.
I noticed that when one of my female classmates mentioned she wanted to go into embedded systems, someone said "that's unusual for a girl" — and the room didn't push back. I didn't push back. I said nothing.
That silence has bothered me ever since.
The Names I Wasn't Taught
Here is something I learned outside of my CS curriculum, in the corners of late-night research:
The first algorithm ever written was by a woman named Ada Lovelace — in 1843. Grace Hopper invented the compiler. Katherine Johnson's calculations put humans on the moon. The spread-spectrum technology underpinning modern WiFi traces back to a patent held by Hedy Lamarr. Radia Perlman invented the spanning tree protocol that makes the internet function. Fei-Fei Li created ImageNet and shaped the entire trajectory of modern AI.
I was not taught any of these names in school.
I was handed a field that women helped build, and I was taught to think of it as having been built without them. Without meaning to, without anyone telling me explicitly, I absorbed a version of this discipline where women were guests rather than founders.
That is not a neutral thing to absorb. It shapes how you see your colleagues. It shapes how you treat them. It shapes the rooms you build when it becomes your turn to build them.
What Being an Ally Actually Looks Like (I'm Still Learning)
I want to be careful here, because "allyship" can become a word men use to feel good about themselves without changing much.
What I have tried to do — imperfectly, inconsistently — is smaller and more specific than a word:
Speak up in the moment. When someone says something dismissive to a female classmate, the window to respond is about three seconds before the conversation moves on and the moment calcifies into accepted reality. I have missed that window more times than I've caught it. But I am getting faster.
Give credit loudly. In group settings, when a woman's idea gets absorbed into the conversation without attribution, I name it: "That was her idea — can we go back to what she said?" This feels small. It is not small.
Stop explaining things that weren't asked for. I have caught myself mid-sentence explaining a concept to a female classmate who neither needed nor requested it. That reflex is worth examining. Repeatedly.
Learn the names. Ada. Grace. Katherine. Hedy. Radia. Fei-Fei. I say them in conversations. I send them to younger students. I refuse to let the history stay edited.
Ghana, and Why This Conversation Belongs Here Too
Gender equity in tech is often framed as a Silicon Valley problem. Pay gaps, pipeline statistics, diversity dashboards. But the ceiling exists here too — it just has different walls.
In Ghana, it lives in the guidance counsellor who steers a girl brilliant at mathematics toward accounting instead of CS — not out of malice, but out of a world that has offered women fewer safe paths. It lives in families who fund their sons' CS degrees without question and gently suggest their daughters choose something "more practical." It lives in the casual import of tech bro culture — from YouTube, Twitter, startup mythology — landing here without the vocabulary that elsewhere has at least begun to name the problem.
I am not separate from this. I was shaped by the same environment. Some of the biases I'm describing are ones I still find in myself when I look carefully enough. That's not comfortable to write. But I think it's more useful than pretending I arrived at allyship fully formed.
Why I Built What I Built
For the Frontend Art prompt of this challenge, I built an interactive canvas piece called "She Compiles the Stars" — 1,800 particles that assemble into a woman's silhouette, a glass ceiling that fractures and shatters when you click it, and the names of six pioneers encoded into the experience.
I built it because I wanted to do something more than observe. Code is my medium. And I thought: if I can use this skill to say these women existed, this ceiling exists, and it can be broken — then that is worth the time.
I also built it to prove something to myself. That I could engage with this subject not as an outsider looking in, but as someone who understands that gender equity in tech is not a women's problem to solve. It is a problem that men — especially men with the ease of walking into rooms without counting them — have both the responsibility and the ability to help fix.
What I Want Other Men to Hear
If you are a man in tech and you have never thought much about this: I'm not here to make you feel guilty. Guilt is not useful.
But I want to ask you to do what I did: start noticing.
Notice who speaks in your meetings and who gets heard. Notice who gets assigned which tasks. Notice who you explain things to unprompted. Notice whose names are missing from the history you were taught.
Then ask yourself what you could do differently. Not perfectly. Not all at once. Just — differently.
The room was built for us. That means we have more power than most to decide what the next room looks like.
To the Women in CS Who Are Still Counting
I see you counting the room when you walk in. I understand now why you do.
I can't promise the count will change as fast as it should. But I can promise that some of us are paying attention — and that we are trying, however imperfectly, to build the room you deserve to walk into without counting.
Written from Accra, Ghana, 2026.
I also submitted a Frontend Art piece for this challenge — "She Compiles the Stars," an interactive particle animation. You can find it here - [https://codepen.io/Aggrey-Paintsil/pen/GgjGwGJ]
Top comments (1)
The framing of "I didn't count the room" is one of the most effective ways I've seen privilege described — not as guilt or accusation, but as an absence of friction you never noticed precisely because it wasn't there for you.
What you're pointing at is that belonging isn't just about being allowed in the room. It's about being able to enter without performing a constant background calculation of whether you belong. That cognitive overhead is real and measurable, and it compounds over a whole degree programme in ways that show up in grades, in confidence, in who gets asked to join projects, in who gets recommended for opportunities.
The fact that you noticed by watching rather than by having the experience yourself, and then took that seriously, is worth naming explicitly. A lot of people in majority positions in their environment never make that observation at all.