The latest articles on DEV Community by Amina Ali (@thedevamina). https://dev.to/thedevamina https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4102664%2Fbd069809-21c0-4f8a-975b-3291fa04b4a1.png https://dev.to/thedevamina en Amina Ali Tue, 01 Sep 2026 06:55:18 +0000 https://dev.to/thedevamina/why-i-call-myself-a-full-stack-developer-not-just-frontend-or-backend-1nm4 https://dev.to/thedevamina/why-i-call-myself-a-full-stack-developer-not-just-frontend-or-backend-1nm4 <p>A lot of developers pick a lane early — frontend or backend — and stay there. I never did, and building ClientIQ is a good example of why.</p> <h2> The problem </h2> <p>Freelancers waste a lot of time figuring out where to post their skills. Upwork? Fiverr? Toptal? The right platform depends on their profile, their niche, and their experience — and most people just guess.</p> <p>I wanted to build something that could actually recommend the right platform based on real data, not gut feeling.</p> <h2> Why this needed a full-stack developer, not two specialists </h2> <p>This is where being a full-stack developer actually mattered:</p> <ul> <li> <strong>The backend</strong> needed a Flask API that could take a freelancer's profile data and run it through a multi-model machine learning workflow to generate a recommendation.</li> <li> <strong>The frontend</strong> needed a clean React interface where users could input their info and see the recommendation in a way that made sense — not just a raw JSON response.</li> <li> <strong>The connection between them</strong> — API design, request/response shape, error handling — needed someone who understood both sides well enough to make them work together smoothly, not just "talk" to each other.</li> </ul> <p>If I had only known React, I'd have needed someone else to build and explain the ML backend to me. If I had only known Flask, the interface would have been an afterthought. Being full-stack meant I could design the whole system as one coherent product, not two separate halves duct-taped together.</p> <h2> What I actually built </h2> <ul> <li>A Flask API that serves multi-model ML predictions</li> <li>A React frontend for input and displaying recommendations</li> <li>A clean handoff between the two — the kind of detail that's invisible when done right, and painfully obvious when it's not</li> </ul> <h2> The bigger lesson </h2> <p>Full-stack development isn't about knowing a little bit of everything. It's about being able to see a product end-to-end and make decisions that make sense for the whole thing — not just your favorite part of the stack.</p> <p>That's the mindset I bring to every project, whether it's a web app, a mobile app, or an AI-powered tool like ClientIQ.</p> <p>I'm Amina Ali, a full-stack developer building web, mobile, and AI/ML products. You can see more of my work at <a href="https://thedevamina.vercel.app" rel="noopener noreferrer">thedevamina.vercel.app</a> or check out the code for ClientIQ and other projects on <a href="https://github.com/thedevamina" rel="noopener noreferrer">GitHub</a>.</p> webdev fullstack react flask