From Low-Code to React Native: My Struggle with Imposter Syndrome and Rebuilding Confidence

Hey folks, hope you're all doing well!

👨‍🔬 From Lab to Code

I started my coding journey almost 5 years ago. I came from a science lab background and jumped into tech, enrolling in computer science at college.

While studying, I worked for 4 years as a developer using a low-code platform. It was a good experience, and I learned a lot—but deep down, I knew it wasn’t the path I wanted to stay on.

It started to feel like I was stuck in that specific technology, and I could see it holding back my growth. I wanted to move into a new stack where I could truly sharpen my skills and build a future with more freedom and challenge.

🚀 New Internship, New Stack

About two months ago, I started an internship at a new company, and I finally got the chance to work on a project using React Native.

Here’s the thing: I didn’t really learn React properly in college—the material was outdated and didn’t prepare me for real-world development. So, I jumped into this project using bits and pieces I’d picked up from online courses, YouTube, and docs.

Basically, I was building the plane while flying it.

😵 And Somewhere Along the Way… I Got Lost

I became overly dependent on AI to write code and solve problems. While it helped me move fast, it also kept me from truly understanding what I was building.

Now, when I look at my codebase, I realize I’ve probably made some bad decisions—messy organization, rushed components, and maybe even architecture choices that won’t scale.

And all of that has left me feeling frustrated, overwhelmed, and drowning in imposter syndrome.

"Am I even a good developer? Do I actually know what I’m doing?"

🔄 Trying to Take Back Control

Right now, I’m trying to get control of the project again… but I’ll be honest, I still get lost a lot.

Some days, I feel like I’m making progress:

• I refactor a piece of code
• I understand something I used to just copy
• I finally connect the dots between parts of the stack

Other days, it feels like I’m just patching holes without knowing how to steer the ship.

I’m collecting knowledge piece by piece—through docs, tutorials, and AI answers—but I can tell I’m missing something deeper. Something more reliable. A stronger foundation.

🌱 Learning to Slow Down

I don’t have all the answers yet.

I’m still figuring out how to:

• Slow down
• Make intentional decisions
• Learn for real instead of just keeping up

It’s hard. But I want to believe this phase is part of the process—even if it’s messy, full of doubt, and not always easy to talk about.

🫂 If You’re Feeling This Too…

If you’re going through something similar—feeling stuck, lost in your own code, or doubting your skills—you’re not alone. I’m right there too.

It’s easy to feel like everyone else has it all figured out, but I think we all go through these chaotic, confusing phases.

Maybe they’re necessary.

Maybe this is just what growth looks like—messy, frustrating, and full of trial and error.

I’m still learning how to rebuild my confidence and make AI a tool I control, not something that controls me.

💬 Let’s Talk

If you’ve been through something like this—or are in the middle of it now—I’d love to hear from you:

What helped you regain control?

How did you push through those waves of doubt?

Let’s talk about it.

No filters, just real dev struggles.