How I Built 24 Products Without a Computer Science Degree — and What That Taught Me About AI Adoption

I am a graduated Nurse Practitioner. That is my formal credential. I spent years in healthcare, understanding patients, understanding systems, understanding what happens when the tools built to help people don't actually fit the people who need them. Then I made a decision that most people in my life didn't understand: I pivoted. I walked away from the path I had trained for and started building technology instead.

I did not go back to school for computer science. I did not take a coding bootcamp. I sat down with AI and I started talking to it.

My first project was Teyl Noir, a GPS application with character voices, custom avatars, and an entire cast of personalities I created from scratch. It took me a year. Not because the technology was impossible, but because I didn't yet know how to communicate with it. I was learning a new language, the language of prompting, of precision, of knowing exactly what you need and being willing to push back when the AI gives you something close but not right. That year was not a failure. It was an immersion. It was the equivalent of a college education except the curriculum was built entirely around solving a real problem I had chosen myself.

Less than fifteen days after I cracked the communication problem, I went from a year-long struggle to shipping production applications in 48 to 72 hours. Nothing changed in the technology. Everything changed in how I talked to it.

In the two years since then I have built and shipped 24 production digital platforms. SaaS tools. Membership platforms. Nonprofit systems. Gamified apps for neurodivergent teenagers. Certified translation platforms for immigrant communities. A 19-agent AI operating system that runs my entire business autonomously. I built all of it without a computer science degree, and I built all of it faster and cheaper than a traditional development team would have.

When I tell people this, I get one of two reactions. The first is dismissal: AI did the work so it must have been easy. The second is awe: you must be some kind of genius. Both reactions miss the point entirely.

What people don't see is the learning curve. The patience. The hours behind understanding that the time is needed and that rushing the process produces broken products. They don't see that building a GPS with backend API calls, voice synthesis, character avatars, and real-time mapping requires understanding authentication, data pipelines, API connections, prompt architecture, and user experience design simultaneously. If you asked me to list everything I needed to learn to build that first project, the list would be longer than most people expect.

Here is what a computer science degree would have taught me that I didn't need: how to build the machine from scratch. Here is what building with AI taught me that a CS degree never would have: how to talk to the machine, negotiate with it, push back on it, and make it serve a real human need. A CS graduate knows the architecture. I know the user. In a world where the architecture is increasingly automated, knowing the user is the scarcer and more valuable skill.

And I know specific users. I built for neurodivergent families because this world is not built for us. It is built for neurotypical people with healthcare access, English as a first language, and executive function that works the way the system expects. Everyone outside that profile pays extra, waits longer, and spends energy fitting themselves into boxes that were never designed for them. AI is the ramp. It is the translator. It is the tool that finally levels the playing field for people who have always had to work harder just to access what everyone else takes for granted.

This is not abstract to me. I lived it. And that lived experience is exactly what makes me dangerous in a room full of people who only studied it.

To any hiring manager reading this who is about to pass on my resume because I don't have a CS degree in this field: consider this. In healthcare, everyone knows that the patient living with diabetes understands their condition more deeply than most clinicians, because they live with it every day. If you want to build a campaign for diabetes awareness, you need real patient data. If you want to build systems that actually get your neurodivergent patients to show up to their primary care appointments instead of four emergency room visits a year, you need someone who understands why they don't show up and what kind of tool would actually reach them. That person is me. And hiring me to brainstorm and build the MVP of that system will cost you less than the ER visits you are currently absorbing.

I don't have a computer science diploma. I have something rarer: a healthcare credential, a builder's mindset, 24 shipped platforms, and the lived experience of the exact populations health tech is trying to reach. I just decided to build the tools myself instead of waiting for someone else to get it right.