This is a submission for the 2026 WeCoded Challenge: Echoes of Experience
I told my wife to keep her phone close. "I might call you to come get me early," I said, already mapping the exit in my head before she'd even pulled away from the curb. Large groups of strangers in new environments are not my thing. Never have been. I had a whole contingency plan: polite excuses, a headache maybe, the classic slip-out-the-back-door if it came to that.
That was this morning, March 8th. International Women's Day. I was walking into a SheBuilds on Lovable event to celebrate by doing something I would not have imagined doing a few years ago: building an app in a room full of people I had never met. Lovable opened its AI app builder for free for 24 hours, powered by Anthropic, and handed every participant $100 in Claude API credits and $250 in Stripe credits. No application. No eligibility requirements. Just show up with a laptop and an idea.
I showed up with both, and a detailed exit strategy I never used.
What I was building
Live music memories fade. You remember the feeling but not the setlist. You remember the venue but not the year. You have ticket stubs in a shoebox or maybe just a mental list that gets shorter every time you try to recall it. I wanted a way to preserve that history and actually see the story it tells about you.
Aftershow Atlas. A personal concert history tracker with an Old Hollywood marquee aesthetic. You log a show you attended (artist, venue, date), and the app pulls the real setlist from setlist.fm, drops a pin on your map, and you enter memory line for each show.
The feature I was most excited about is Musical DNA. It reads your concert history and tells you who you are as a music fan. Not stats. Interpretation. "A devoted alternative rock archaeologist who excavates the grittiest gems of the '90s underground, returning again and again to worship at the altar of Shirley Manson's defiant anthems. They chase the raw, unpolished edge of rock's rebellious daughters across continents, from Dublin's punk halls to Mexico's intimate venues." That kind of thing.
I had spent the night before building out the full brief with Claude: design system, database schema, edge functions, accessibility requirements, a 14-section build document. I came prepared. What I did not come prepared for was how the day would actually feel.
What happened in the room
Christina, our host, gave us about an hour and twenty minutes to build. I remember her announcing that time was up and genuinely not believing it. How? We had just gotten here.
But that is the thing. We did not just build. We got to know each other first. And then, even while building, I talked to Billie, Alison, and Kushboo about what they were working on, what they were experiencing, what problems they were trying to solve. Sharing ideas with strangers. Getting excited about someone else's project. Offering a suggestion. Asking a question you were not sure was smart enough to ask.
I do not think I spoke with a single builder who had an engineering background. Not one. And they were all building something that mattered to them.
The builder identity
One of the conversations Christina led, and I keep coming back to, was about embracing the builder identity. Not the engineer identity. Not the developer identity. The builder identity.
We may not be building unicorns. Our apps might stay at v1 forever. The code might not be elegant by anyone's standard. But we are building. We are taking up space and filling it with our ideas, our products, our passions. And we are doing it together, which means we get to shine in our strengths and support each other through the parts that are hard.
That reframe mattered to me. Because when you come from courtroom operations, not computer science, when you learned to build by directing AI tools instead of writing code from scratch, calling yourself a builder can feel like you are borrowing someone else's jacket. Christina made it clear that the jacket fits.
Where I come from
I spent years managing courtroom operations before I ever touched a codebase. My path into tech was not a boot camp or a CS degree. It was curiosity, AI tools, and a stubbornness about building things that actually help people.
I do not write code from scratch. I provide creative direction and validation. I work with a handful of AI tools, compare their outputs, choose the best pieces, and stitch them together into something that works. The AI generates. I direct, validate, and refine. That is a deliberate workflow, not a limitation.
The point is not that engineering degrees do not matter. They do. We need people who can read code, write code, and help the rest of us fix our mistakes. The point is that there is more than one path to building something worth using, and mine started in a courtroom.
What I keep waiting for
I keep waiting for the part where I have to be cynical about this. The part where I hedge, or qualify, or add the "but of course, it is not all sunshine" paragraph so it does not sound naive.
It has not come yet.
Nobody in that room felt like they had to perform. Nobody was networking in that calculating way where you can feel someone scanning for your job title. People showed up. People built. People helped each other. Product.io hosted us, Christina put the whole thing together, and the energy was just... great.
When you spend enough time building alone in an echo chamber (solo builder anyone?), or showing up to spaces that feel curated or transactional, you notice when one feels different. This one did.
Who this is for
If you are reading this and you do not have a tech background but you have been thinking about building something, this is for you. If you are in an underserved community wondering whether the tools and the spaces and the support actually exist, they do.
If you want to be a founder, help others, invest in your community, or just finally build that idea that has been sitting in your notes app for six months, it feels like the barrier is lower than it has ever been. I built Aftershow Atlas as a solo builder with no engineering background and a very detailed brief. If I can do that, I think a lot of other people can too.
The app
Aftershow Atlas is live. It is not perfect. The auth flow gave me trouble (Google OAuth was a disaster, we pivoted to magic link mid-event). Lovable ran out of Claude credits partway through, and we kept going anyway. The marquee bulb animation is maybe a little extra. The Musical DNA feature still needs more show data before it really sings.
But it exists. Because I showed up to a room full of strangers on International Women's Day, did not call my wife for an early ride home, and built something.
Built at SheBuilds on Lovable on March 8, 2026, celebrating International Women's Day. Powered by Lovable, Anthropic Claude, Supabase, and the setlist.fm API. Thank you to Christina, Product.io, and every builder in that room.
Check out Aftershow Atlas or find me on GitHub: @earlgreyhot1701D
Top comments (0)