I’m a passionate frontend developer dedicated to helping founders and business owners elevate their digital presence. I specialize in crafting visually stunning, user-friendly interfaces that prioritize seamless user experiences. By optimizing design and functionality,

8/ #DeveloperJourney #OpenSource #FrontendDevelopment #WebDev #TechTwitter #HNGInternship #Learning #Programming #BuildInPublic

My frontend lead might never have followed up if I hadn’t asked. And I might never have learned this lesson. Sometimes, growth doesn’t come from success. It comes from a pull request that didn’t get merged.

Simple, but it changes everything about collaboration and review. That small mistake taught me two big lessons: 1️⃣ Always ask questions — even when you think you should know the answer. 2️⃣ Leverage tools to learn — docs, AI, or mentors. Don’t stay stuck. Create PR → same repo

Create a new branch Push my changes to that branch Here’s the key difference 👇 🔹 Fork workflow → for open-source projects where you don’t have write access 🔹 Branch workflow → for team projects where you do have access

So I went to https://t.co/csZCfGs03a, and everything finally made sense. Here’s what I learned: ❌ What I did (wrong) Forked the main repo Cloned my fork Made changes there Created PR from my fork → main repo ✅ What I should’ve done Clone the main repo directly

You were expected to create a branch in the main repo.” I was confused. I’d contributed to open-source projects before — forking and making PRs was the standard, right? But clearly, not this time. Still, I didn’t want to bother him with more questions.

A day passed. Then two. Then five. No feedback. No merge. So I reached out again — and that’s when I got a reply I wasn’t expecting 👇 “Your PR is from your personal repo which shouldn’t be. Several files are trying to override existing ones.

I thought I knew how to contribute to a project… until yesterday. A few weeks ago, I requested to contribute to a repo, got permission, completed my task, pushed, and made a pull request. Then I waited for the frontend lead to review it.

Every task felt impossible… until it wasn’t. 🌸 The biggest lesson? Growth hides behind discomfort. If you’re too comfortable, you’re not growing. — 2 weeks down. A lot more growth to go 🚀

1️⃣ Met Twig for the first time (a PHP templating language I didn’t even know existed) 2️⃣ Read through Vue.js docs and built components 3️⃣ Integrated Convex for backend 4️⃣ Used Resend to send confirmation emails 5️⃣ Touched React Native for the first time

I used to think internships were just “learning opportunities.” Until I joined the @hnginternship . 2 weeks in… I’ve learned more than in months of tutorials — and it’s been hard. Here’s what I’ve learned 🧵👇

This guy landed a foreign client without Upwork, Fiverr, or LinkedIn for 4 years. He found them on Slack. Now he works from home, gets paid in dollars, and teaches the same method to others. Here’s exactly how he did it (and how you can too): 🧵

I’m Azubuike Chima, an e-commerce frontend dev helping brands build high-converting sites. DMs open! 💬 #stripe #buildinpublic #react #ecommerce

What would you do if your dream design had no desktop version? It’s been great seeing this project evolve — from listings, to search, to now a functional cart 🛒 Next up: Checkout + Stripe integration for payments 💳 Bit by bit, it’s coming together. — #frontenddevelopment

Curious — do you plan your tables fully before building? Another challenge: the Figma file I’m using has no desktop version. So I’ve had to improvise a lot. If you ever work on a mobile-only design — make sure you have a plan for desktop early on.

2/ This is my first time using Supabase — and honestly, I love it. It’s powerful yet simple. My main challenge? Constantly altering my product table. Mostly because I didn’t have the full product schema mapped out from the start.

Just wrapped up the Cart Page for the e-commerce app I’ve been building. This one was tricky — getting the flow right (add, update, remove, total) sounds simple, but it ties together so many moving parts — state, UI feedback, and logic. #buildinpublic #nextjs #supabase

What are you working on? What are you building? Do you want a store for your business or in need of a website, SEND A DM.

This is me showing up and building in public. I will be building this project in public from start to finish. To be honest, I want to push myself with this project. To learn. To Grow. I want to develop this project the right way. Using the best practices. The right set-up.

The stacks I will be using are: Typescript NextJS Tailwind Supabase TanStack Query Zustand. This is my first real project using Typescript. A friend promised I am going to love it. Thank you for this Push.