The sentence comes out almost automatically: I'm not technical.
You say it before opening a spreadsheet formula. Before clicking into a settings page. Before agreeing to take a look at the website. It's a small pre-apology, a way to manage expectations downward before anyone else gets the chance to. Most women we know say some version of it, often, and often about things they are actually quite good at.
There are a lot of reasons for this. None of them are your fault. All of them are well-documented. This isn't a post about why. It's a post about a quiet thing that's starting to happen anyway.
Women are building their own apps on the side. Not in bootcamps. Not in "learn to code in 100 days." Through specs.
A spec is a blueprint you paste into Claude Code. It tells the AI what to build, in plain English, step by step. You run it. You get a working app. That app lives on your machine: a grocery planner, a cycle tracker, a client invoicing tool, a reading journal, whatever you've been wanting. No subscription. No login. Yours.
Here's the part that isn't in the marketing copy: after the app is built, the code is right there. You can open it. You can read it. At first it looks like hieroglyphics. By your second or third spec, you start to recognize the shapes. The word function starts meaning something. You notice that the thing you typed in English ended up corresponding to a thing in the code, and you can find it, and if you squint you can even change it.
That's coding. Not in the way a recruiter means coding, but in the way that matters for confidence: you are now a person who has looked at a working program and understood, in a loose way, how it works.
There's a compounding effect that's easy to miss.
- Spec one. You ran a blueprint and got an app. You barely touched the code. You feel slightly powerful.
- Spec two. You changed one line: a label, a color, a default. It worked. The feeling doubles.
- Spec three. You hit a bug, read the error message instead of closing the laptop, and asked Claude to fix it. It got fixed. You are now someone who debugs.
- Spec four. You look at a spec in the marketplace, see what it's supposed to do, and think: I could write that.
The sentence you open with starts to shift. I'm not technical slowly becomes I build my own tools. You haven't taken a bootcamp. You haven't changed careers. You've just stopped flinching.
There's a long and uninspiring tradition of telling women that the fix for their underrepresentation in tech is another bootcamp, another cohort, another year of evenings spent on a curriculum that didn't expect them and wasn't built for them. Specs aren't that. Specs are the side door. You don't have to declare yourself technical. You don't have to sit in the front row of a classroom that might as well have a sign on the door. You just build the thing you wanted, and the fear quietly moves out of the house.
You don't have to become a developer. That was always the wrong goal anyway. The goal is to be someone who, when she wants a tool that doesn't exist, builds it.
Pick a spec. Run it. Break it. Run it again.
There's a version of you, maybe a year from now, maybe less, who catches herself about to say I'm not technical, and doesn't. Who says, instead: hang on, let me build that.
She's already on the other side of the door. You just haven't met her yet.
