I Said 'That's Not For Me' For Weeks. Then I Built an App

I have a background in psychology and work in HR.

Outside of my day job, I write a well-being blog and host workshops and coaching sessions to help people know themselves better, improve their overall well-being, and find their ideal career.

I also know how to write R code — the kind used for statistical analysis and research. So I'm not someone who is completely allergic to computers. But writing R scripts and building an actual app that real people can use? Those are two completely different universes.

For a long time, I told myself a very convincing story: I can analyze data. But I cannot build things. That world is not for me.

I want to tell you how that story almost kept me from doing one of the most meaningful things I've ever done.

And I want to tell you this because I've already seen what happens when people watch someone like them do something they thought was out of reach. It changes things. That's exactly why I'm writing this.

---

My Husband Tried to Tell Me For Weeks

Before I get to the LinkedIn moment, I have to tell you about the weeks before it.

My husband uses Cursor — one of the main AI coding tools — for his own work. He had seen what it could do. And for weeks, he kept nudging me.

"You should try vibe coding. You could build something."

My answers were consistent and creative in their avoidance:

"I'm too tired after work."

"That's not really for me."

"Maybe at the weekend." (The weekend would arrive. I would not vibe code.)

I wasn't being dismissive. I genuinely believed what I was saying. I had a full-time job, a blog, workshops to run, a life to manage. And more than the tiredness, I think I believed — quietly, without fully examining it — that building things was a specific kind of skill that I simply didn't have. That there was a type of person who built apps, and I was a different type of person entirely.

My husband, to his credit, kept nudging anyway.

And then one evening, everything changed. Not because of anything he said. Because of something I saw.

---

It Started With a LinkedIn Post

I wasn't looking for a sign. I was scrolling LinkedIn — the way we all do, half-present, half-distracted — when I saw a post from an old coworker.

They were vibe coding a website. Live. In real time.

For those who don't know what vibe coding is: it's building software by describing what you want in plain language to an AI, and having it write the code for you. No computer science degree required. No bootcamp. No prior experience building products.

But this wasn't a developer. This wasn't someone who had spent years learning to code. This was someone I knew. Someone from a similar background to mine. Someone who, as far as I knew, was not a "technical person" in the traditional sense.

And there they were. Building something.

My reaction was not wow, how impressive. It was something much more personal than that.

It was: if they can do it, I can do it.

Not a grand declaration. Just a quiet, firm recognition — the kind that lands in your chest before your brain has a chance to talk you out of it.

Weeks of my husband's encouragement hadn't moved me. One LinkedIn post from someone who looked like me moved me immediately.

I'm not saying that to diminish his encouragement — which, in retrospect, was laying the groundwork the whole time. I'm saying it because I think it's important to understand how inspiration actually works. It's not always the person closest to you who finally unlocks it. Sometimes it's seeing a stranger from a similar background do the thing, and realizing with sudden clarity that the wall you've been staring at was never actually a wall.

I closed LinkedIn. Opened YouTube. Found a Cursor tutorial — you can watch the same one I used here.

An hour later, I had it set up and running.

An hour. That's all the setup took. And whenever I got stuck following the tutorial, I just opened ChatGPT and asked my question in plain English. It answered. I kept going.

I tell you this because I want to be specific about how low the actual barrier was. Not the emotional barrier — that was real and I'll get to it. But the practical, logistical barrier of getting started? One hour. One YouTube video. One AI to answer my questions.

The thing that had felt like a wall was actually a door. I just needed to see someone like me walk through it first.

---

The Moment I Actually Sat Down to Begin

I want to be honest about what that first session felt like, sitting down with Cursor for the first time.

I stared at the screen. And I had absolutely no idea what to type.

I know R. I know how to run a regression. I know how to clean a dataset. But staring at a blank project with no file structure, no starting point, nothing — that was a completely different kind of not-knowing. The kind that makes you feel like a complete beginner all over again, regardless of what you already know.

This is the part nobody tells you about. They show you the finished product. They show you the moment of triumph. They don't show you the sitting there, feeling stupid, wondering if you've made a terrible mistake and questioning every life choice that led you to this moment.

I study and teach human behavior for a living. I am supposed to know things.

And in that moment, I knew nothing.

It sounds small when I write it out. But I think this is the exact moment most people quit before they even begin. Not because the task is actually impossible. Because the feeling of not knowing where to start is so profoundly uncomfortable that we'd rather retreat to the safety of what we already know we're good at.

I almost did that.

Instead, I typed my first message to Cursor.

It was probably the most inelegant prompt ever written. Something along the lines of: I want to build an app where people can upload their personality test results and get a personalized report. I don't know how to build apps. Can you help me figure out where to start?

And then something happened that I was not prepared for.

It answered. Clearly. Helpfully. Like a collaborator who had been waiting for me to show up.

---

Two Weeks of Evenings

I built the first working version of this app in two weeks, working a few hours after work every other day or so.

Not full days. Not a sabbatical. Not some heroic coding marathon. Just ordinary Tuesday evenings and Saturday afternoons, carved out around a full-time job and everything else life requires.

I need you to hold that for a second. Two weeks of stolen hours. That's all it took to go from I have no idea how to build this to this thing actually exists and works.

I won't pretend those two weeks were smooth. They were not.

I cannot tell you how many times I would get something working, feel briefly triumphant, and then come back the next day to find it had somehow broken in my absence. I would describe a feature to Cursor, it would write the code, and the result would be almost right — but not quite. So I'd try again. And again. And again.

Sometimes it took five or six attempts to get one thing right. Sometimes more. I still can't always predict which requests will be straightforward and which will spiral into an hour of troubleshooting. That part hasn't fully changed.

My personal favourite example: the Mandarin translation feature.

The app has a simplified Chinese language option — useful for the Chinese-speaking community I work with. Getting it to work sounds straightforward. Click a button, everything translates. Simple.

Except it wasn't. The first version translated about 70% of the page and left the rest defiantly in English, with no apparent logic for which parts it had decided to ignore. Then, once I got the text mostly working, the charts had their own feelings about the situation. The labels wouldn't translate. Then they translated but landed in the wrong positions. The y-axis text kept migrating to places y-axis text has no business being.

I fixed it. Then something else broke. I fixed that. The y-axis moved again.

I cannot tell you how many attempts it took to get a fully translated page where all the text was in the right place, including — finally, mercifully — the axis labels on the plots.

I laugh about it now. At the time, at 10pm on a Wednesday, I was having a deeply personal argument with a chart.

But I fixed it. Every single time, I described the problem, tried again, and eventually it worked. That's the whole process, distilled into one maddening and completely instructive example.

Here's what I learned: the process of trying, failing, adjusting your description and trying again is not a sign that you're doing it wrong. It is the process. It's what building actually looks like for everyone, technical or not. The difference is that now, you don't need to understand why something failed at a code level in order to fix it. You just need to describe the problem clearly and keep going.

---

What I Learned About Identity Before I Learned Anything About Code

Here's what I've learned from years of studying in psychology: we are deeply attached to our identities. Who we believe ourselves to be shapes what we allow ourselves to try.

If you believe you are "not a technical person," you will avoid technical things. Not because you can't do them — but because attempting them threatens the story you've built about yourself. And our brains are extraordinarily good at protecting our stories.

I had protected mine for years.

I'm the ideas person. The people person. The psychology and HR person. The researcher.

The unspoken other half of that sentence was: not the builder. Not the one who makes actual products.

Building this app forced me to sit with the discomfort of not knowing — which is, ironically, exactly what I help other people do in my workshops. I help people challenge the stories they tell about themselves. I help them see that their identity is more flexible than they think.

It turns out I needed to take my own workshop.

---

The Moment It Worked

I want to tell you about the first time the app actually did what I had imagined it doing.

A user uploads their Big Five personality results — a PDF from an external site. The app reads it. Generates a personalized report. Shows their trait profile with charts. Reflects back who they are in language that's warm, specific, and psychologically grounded.

When I saw it work for the first time — really work, the whole flow, end to end — I just sat there for a moment.

I have run dozens of workshops where I ask people to go to five different websites, take five different assessments, screenshot every result, and somehow piece it all together. I have always known that was the weakest part of the experience — the friction, the scattered screenshots, the impossibility of tracking how someone's results change over time.

And now, in front of me, was a single tool that did all of it. That I had built. In two weeks of evenings after work.

I don't have a better word for it than this: it felt like a dream I hadn't quite let myself fully have came true.

---

What the App Actually Does

The app lets people take science-backed assessments — Big Five personality, vocational interests, character strengths, personal values, and more — or upload results they've already completed elsewhere. It generates a personalized report covering their core traits, values, strengths, and career interests. And it tracks results over time, so you can see how your profile evolves across multiple reports.

That last part — tracking over time — was something I had wanted for years. Both for myself and for the people I work with. There's something powerful about being able to look back and see: this is who I was six months ago. This is who I am now. Here's what changed.

The newest section generates three specific AI-powered ideas for a business, career move, or side project tailored to each person's unique profile. Not generic advice. Actual, specific possibilities that emerge from the intersection of who you are and what you want.

I built this because I kept seeing the same thing in my workshops: people who were smart, capable, and deeply stuck. Not because they lacked talent. Because they lacked self-knowledge — a clear picture of who they were and what they were actually built for.

I wanted to build something that gave people that picture.

And now, improbably, it exists.

---

Then We Threw a Party to Prove It Wasn't Just Me

After I finished the app, I had a thought.

If I could do this — with no app-building experience, in stolen hours after work — what would happen if I put a group of regular people in a room together and asked them to try?

So my husband and I did something a little unconventional. We invited friends over on a Sunday afternoon. Cleared the dining table. Made it feel like a gathering, not a class. And for three hours, everyone built something.

Not everyone was technical. Not everyone had coding experience. They came from all kinds of backgrounds — finance, research, creative fields. The one thing they had in common was that none of them had built an app before.

Here's what they walked away with, three hours later:

One friend built a crypto exchange platform — a tool to make it easier to convert between different types of cryptocurrency, something he'd been frustrated by for years as someone who trades regularly.

Another built her first personal website. A portfolio, clean and professional, ready to send to employers. She had been putting this off for months because she thought she needed to hire someone to do it.

A researcher built a tool that allows one-click download of multiple academic articles at once — solving a problem she encounters literally every single day at work, that she had simply accepted as an annoying fact of life.

Three hours. Three complete beginners. Three things that now exist in the world that didn't exist that morning.

I watched each of them hit that moment — the moment it first worked — and I recognized the look on their faces immediately. Because it was the same look I'd had sitting alone at my laptop a few weeks earlier.

Oh. I can do this. I actually just did this.

That look is why I do the work I do. That look is what I want to spend the next chapter of my career multiplying.

Because here's what that Sunday afternoon confirmed for me beyond any doubt: this is not a skill that belongs to a certain kind of person. It is not gated by your degree, your job title, your age, or whether you've ever written a line of code in your life.

It belongs to anyone who has a problem they understand deeply and the willingness to describe it out loud.

That's it. That's the whole requirement.

---

The Three Things That Actually Make the Difference

After building my own app and watching a room full of first-timers build theirs in a single afternoon, I've noticed that the people who succeed aren't the ones with the most technical background. They're the ones who get three specific things right from the start.

1. Start with something you genuinely care about.

This sounds obvious. It isn't.

The temptation when you first sit down with an AI coding tool is to think: what's a good app idea? As if the right answer is somewhere out there, waiting to be found.

It's not. The right answer is already inside you — in the problems you live with every day, the ideas you've been quietly carrying, the things you love doing and wish were easier.

Ask yourself one of these:

What problem have I been trying to solve in my own life? 

Maybe you're a parent drowning in appointment scheduling and you want a simple family organizer. Maybe you're a freelancer manually tracking invoices in a spreadsheet and there's got to be a better way. The fact that you feel this frustration daily means you understand the problem better than any developer who's never lived it — and that understanding is your biggest asset.

What business idea have I been sitting on? 

Maybe you've always thought someone should build a platform that matches local artists with restaurants looking for decor. Maybe you've imagined a subscription box service but never knew how to build the website for it. The prototype you build in an afternoon won't be the finished product — but it will be real enough to show people, test, and build on.

Is there something you simply love doing? 

You don't need a grand career vision to start. One person at our workshop built a tool to solve a daily frustration at work. Another just wanted a personal website that felt like them. And if you love playing games — you can build a game. Seriously. Your passion for the thing is what will keep you going when it gets hard.

The people who stall are the ones who try to think their way to a good idea. The people who build are the ones who start with something that already matters to them.

2. Grab a friend — or at least tell one.

I did not build my app alone. Not really.

When I got stuck — which happened regularly — I opened ChatGPT and asked questions in plain English. I talked through ideas with my husband, who uses Cursor for his own work. And when we ran the workshop, everyone was in the same room, figuring it out together, laughing at the same frustrations, celebrating each other's wins.

That social layer is not optional. It's what keeps you going past the first evening.

So before you open Cursor, do this: tell someone what you're building. A friend, a partner, a family member, a coworker. Describe it out loud. Let them ask questions. Let them get curious. Even better — invite them to build something alongside you.

There's something about saying I'm building a thing and you're watching that makes it much harder to quietly give up. And there's something about having someone ask hey, how's that app coming? that will motivate you to open the laptop on the evenings when you really don't feel like it.

My husband nudged me for weeks before I started. I rolled my eyes every time. And then I built the thing, and the first person I wanted to show was him.

Accountability isn't a productivity hack. It's just what humans have always needed to do hard things. Use it.

3. Deploy it — so real people can actually use it.

This one is the step most first-time builders skip. And it's the most important one.

Building something that only lives on your laptop is satisfying for about two days. Then it starts to feel like a tree falling in the forest with no one around to hear it.

Deploy your app. Put it on the internet. Send the link to your friends and family.

I use Vercel, which takes a working app and makes it publicly accessible in minutes — genuinely minutes. If you've never heard of it, there's a great tutorial here that walks you through the whole process.

Here's why this matters so much: the moment real people start using your thing, everything changes. You get feedback. You see what confuses them. You notice what they love. And — this is the part I didn't fully anticipate — you feel a kind of motivation that no amount of solo building can generate.

When my app went live and the first person who wasn't me generated a report, I felt a responsibility I hadn't felt before. A pull to make it better. Not because I had to, but because someone was actually there, on the other end, using something I had made.

That feeling is what turns a weekend project into something you keep building.

---

One More Thing Nobody Warned Me About: It's Addictive

I want to be honest with you about something.

I thought building the app would feel like work. Like pushing through. Like the kind of effortful, teeth-gritting discipline you need to do something hard.

It didn't feel like that at all.

It felt like flow.

If you've ever been so absorbed in something that you look up and two hours have disappeared — that's what vibe coding feels like once you get going. You describe something. It appears. You describe the next thing. That appears too. You're not fighting the tool. You're collaborating with it. And there's something almost intoxicating about watching ideas become real in real time, faster than you've ever experienced before.

I found myself opening the laptop at 10pm not because I felt obligated to but because I genuinely wanted to see what I could build next. That almost never happens with things that are hard and unfamiliar. It happened constantly with this.

Part of what makes it so compelling is that you're not just building something — you're experiencing firsthand what AI can actually do right now. Not through a news article. Not through a podcast. Not through someone else's description of it. You are in it, working alongside it, watching it write code that works, watching it solve problems you couldn't have solved alone. It gives you a visceral, personal understanding of where AI actually is in 2026 that no amount of reading can replicate.

And here's what surprised me most: the more I built, the less afraid I became.

---

How Building Something Quietly Dissolved My AI Anxiety

I'll admit something I haven't said out loud much.

Before I started building, I had anxiety about AI. Not in a dramatic way. But in the low-level, background hum kind of way that I think a lot of people are carrying right now. The what does this mean for my career, my skills, my relevance kind of anxiety.

The news about AI is relentless and it is not designed to make you feel calm. Every week there's a new headline about what AI is replacing, disrupting, making obsolete. It's easy to feel like you're watching something happen to you rather than participating in it.

Building changed that. Completely.

There is something about taking action — any action — that anxiety cannot survive. Not because the action solves the problem, but because it moves you from passive observer to active participant. You stop watching AI happen on a screen and you start working with it at a table. That shift is profound in a way that is difficult to fully describe until you've felt it.

I am not less aware of how much AI is changing things. I am just no longer afraid of it in the same way. Because now I know — in my body, not just my head — that I can learn to use these tools. I have proof. I built something.

---

Why This Matters More Than You Might Think for Your Career

Now that I've built my first app, something else has shifted too.

I feel confident in a way I didn't before — not just about this app, but about my ability to learn new tools in general. There's a compounding quality to it. Each thing you build teaches you something that makes the next thing easier. Each new tool you try expands your sense of what's possible. I'm not just working on one app anymore. I'm building a portfolio — a collection of AI-built tools and projects that I can point to and say: this is what I know how to do.

And that portfolio matters. Enormously. Right now.

Employers are not just talking about wanting AI skills. They are actively looking for people who can demonstrate them. Not in theory. Not on a resume line that says "familiar with AI tools." In practice. With evidence.

If you already use AI extensively in your day job, you have that evidence. But many people don't. Their current role doesn't require it. Their company hasn't integrated it yet. They know AI is important but have no way to show it.

Vibe coding your own app in your free time solves that problem completely.

Think about what it signals to show up to an interview and say: I built this. Here's the link. You can use it right now. It doesn't matter if it's a simple tool or a small project. The fact that it exists — that you went from idea to deployed product using AI — demonstrates exactly the kind of initiative, adaptability, and practical AI fluency that employers are trying to assess and struggling to find.

You don't need permission from your job to build your AI portfolio. You can start this weekend.

---

What This Has to Do With You

I'm writing this article because of what I've seen happen when people watch someone like them do something they thought was impossible.

I saw an old coworker's LinkedIn post and it unlocked something in me that weeks of encouragement from my own husband hadn't managed to move. Not because his encouragement didn't matter — it did, more than he knows — but because there is something uniquely powerful about seeing someone from your specific world, your specific background, your specific type of career, do the thing.

That's what I'm trying to be for you right now.

The barrier to building something in 2026 is not technical skill. I work in HR with a psychology background and some R coding experience. None of that is why I was able to build this. What made the difference was seeing someone like me do it first — and realizing that the story I'd been telling myself about who gets to build things was just that. A story.

If you have been telling yourself that you're "not technical," I want to challenge that story the way I challenge every limiting story I encounter in my work.

You do not need to learn to code. You need to learn to describe what you want clearly — which, if you've made it this far in this article, you are already capable of doing.

You need to be willing to feel stupid for a little while at the beginning. Which, I promise, gets easier.

And you need to have something you actually care about building. Something that comes from your specific knowledge, your specific experience, your specific frustration with how things are.

That thing — whatever it is for you — is your unfair advantage. No AI can replicate it. No developer who doesn't know your world can build it as well as you can.

Find your LinkedIn moment. Find the person from a background like yours who has already built something. Let their existence be the proof you need. Because once you see that someone like you can do it, the question stops being can I? and starts being what am I waiting for?

---

The Thing I Keep Coming Back To

I think about the version of me who said I'm too tired after work for weeks.

She wasn't lying. She was tired. She was also protecting a story about herself that felt safer than the alternative.

I'm glad she eventually closed LinkedIn, opened YouTube, and spent one hour setting up a tool her husband had been telling her about for weeks.

Not just because the app exists now. But because of what the process taught her — taught me — about what becomes possible when you're willing to be a beginner again. About how much of what we call "I can't" is actually "I haven't yet." About how the expertise you've spent years building is not separate from the world of building things. It is the most important thing you bring to it.

If you're sitting somewhere right now with an idea you've been carrying — an app, a tool, a product, something that would solve a problem you know intimately — here is the only thing I want you to take from this article:

You don't need to know how to build it.

You just need to be able to describe it.

Open Cursor. Watch this tutorial to get set up in an hour. Type what you want. See what happens.

The rest, I promise, you can figure out as you go.

---

The App I Built to Take This Further

That Sunday workshop confirmed something I had already started to believe while building my own app: self-knowledge is the missing ingredient in almost every career conversation happening right now.

People are being told to "learn AI." To "future-proof their skills." To "pivot." But none of that advice lands without a foundation — without knowing who you actually are, what genuinely energizes you, and what you're specifically built to do.

So I built a tool to give people that foundation.

It's designed specifically for people who are navigating their careers in the age of AI — whether that means you or someone you know who fits one of these:

You're worried about AI replacing your job — and you want to understand how to stay ahead and use AI as a tool to build something, rather than fear it.

You have an idea but don't know where to start — you've always wanted to build a business, app, or side project but haven't had the clarity or confidence to begin.

You're ready for a career change — you feel stuck in the wrong role and want real data, not generic advice, to help you figure out the right direction.

You want to use AI but don't know how — you want to leverage AI tools in your own life and work, but need a personalized starting point that actually makes sense for you.

Here's how it works:

Step 1 — Know Yourself. Take science-backed assessments on your personality, values, strengths, and career interests. Or upload results you've already completed elsewhere. The more you complete, the more personalized your results.

Step 2 — Get Your AI Report. Receive a personalized report that reflects exactly who you are — your core traits, what drives you, and where you shine most brightly. It's the kind of clarity that usually takes months of coaching to arrive at.

Step 3 — Build Your Next Chapter. Get 3 specific, tailored ideas for careers, businesses, or projects that match your unique profile — plus a concrete first step you can take this week, calibrated to exactly where you are right now.

It's free to start. No technical background required.

Try it here.

And if this article resonated — if you're one of the people I described above — I'd love to know what your report says about you. Share it in the comments, or send me a message.

---

Like, Comment & Share

Please like this post and leave a comment if you found it helpful and share it with others who may benefit from seeing this!

As always, feel free to reach out to me at jytian188@gmail.com with any questions you have or anything else you'd like help with!