I used ChatGPT, Claude, and Gemini to build the same project. Here's what actually happened
So last week I had a small project due and basically no time left for it. Instead of just opening whatever AI tool I usually default to, I had this slightly dumb idea: build the exact same thing three separate times. Once with ChatGPT, once with Claude, once with Gemini.
Same prompt for all three. Same idea, same deadline breathing down my neck, same everything really.
I wasn't trying to crown a winner or anything dramatic like that. I just wanted to know, if I had to pick ONE of these for college work, internships, or some quick startup build, which one would actually save me time without leaving me to clean up the mess afterward. That question's been bugging me for weeks honestly, ever since a senior in my batch said something offhand about "just pick one and stick with it," and I couldn't tell if that was good advice or just laziness dressed up as wisdom.
The project I picked
Kept it simple. A small to-do list app, login, task categories, basic dashboard. Nothing groundbreaking, it's the kind of project that shows up on every "build your portfolio" list out there.
I picked it on purpose though. It's easy enough that other students could follow along, but it's got enough moving parts (login, database, UI) that it'd actually show real differences between the tools instead of all three just spitting out the same boilerplate.
Gave all three the exact same first prompt, word for word. No follow-up tips, no "oh, also can you add this." Just the raw prompt, then I sat back and let each one do its thing.
Side note, I almost gave up on this whole idea halfway through because my laptop decided to restart and update itself right when ChatGPT was mid-response. Lost about ten minutes to that. There was also a power cut for like two minutes in between, which is just normal life here, but it threw off my timing comparisons a bit. Anyway, moving on.
Round 1: ChatGPT
Here's how it went with ChatGPT:
- Fast. File structure, basic UI, and login logic, all within seconds.
- Sounded confident the whole time, like it was presenting to a client almost. A bit too polished if I'm being honest.
- Ran the code. Two things broke.
- Not huge bugs, but exactly the kind that'd make a beginner panic for a good 20 minutes trying to figure out what went wrong, because the error messages didn't really point to the actual problem.
- Fixed both once I pointed them out, pretty fast actually.
- The catch, obviously, is that I had to spot them myself first. If you're new to this, that's the scary part, you might not even know what to flag.
Round 2: Claude
Claude went about it pretty differently:
- Broke the project into smaller pieces instead of dumping everything at once, and explained why as it went.
- Notes-taking moment for me, not gonna lie.
- First try, ran almost perfectly.
- Only fix was a missing dependency. One line. Done.
- Later, follow-up question about scaling (more users down the line eventually). Didn't just answer it.
- Pointed out an issue with how I'd structured my database before I even asked. That's senior-dev-in-a-code-review territory.
- Caught me off guard, getting that for free without asking.
Round 3: Gemini
And then Gemini, which surprised me in a different direction altogether:
- Strong point was somewhere I wasn't expecting, research and context mainly.
- Asked which libraries to use. Got back an actual comparison, pros and cons for each, like something out of a research paper.
- Useful if your project involves a lot of "which option do I even go with" decisions.
- Code itself, solid. Just more verbose than the other two though.
- Some parts read like it was explaining things for a tutorial audience instead of just handing me working code.
- Fine if you're learning. Slower if you need it done in the next hour, which, in deadline week, I did.
- Random thought, but it reminded me of those long YouTube tutorials where the guy spends five minutes explaining what a variable is before getting anywhere near the point. Not bad exactly, just very noticeable when you're in a hurry.
So which one actually won
Here's the part I didn't see coming. There wasn't really one single winner, it depended on what I cared about at each step:
- Speed first, don't mind fixing small stuff yourself afterward? ChatGPT, no contest.
- Code that mostly works first try, plus feedback you didn't even ask for? That was Claude.
- Still learning, want the context and the code together? Gemini wins there, even if it takes longer to get through.
For my specific project, something I needed working AND needed to be able to explain later in a viva or interview follow-up, Claude ended up being my pick. Not because it's objectively "the best" or whatever, just because it matched what I needed right then.
Depends on who you are, honestly
If you're a student working on assignments or final year projects, that debugging gap probably matters the most to you out of everything I mentioned. Catching its own mistakes before you even see them saves you from those late night "why is this not working" spirals.
Founders or people building something early stage might find more value on the research side, the stuff Gemini was doing, picking libraries or frameworks before committing real time to actually building something.
Devs who just want clean code without much back and forth, well, you already know which one I'd point you toward at this point.
My honest take
None of these are bad tool. I don't think that's really the debate anymore in 2026, if it ever was. It's more about which one fits your workflow, your skill level, and how much time you've actually got on a given day.
If you've got a spare hour sometime, try this yourself. Pick something small, run it through two or three tools, and actually pay attention to the process instead of just the final output. You'll learn more about how you work than how the tools do, probably, which wasn't really something I expected going into this whole thing.
Anyone else tried something similar? Curious whether your results matched mine or went completely differently. Drop it below if you have, I'll actually read through the comments this time unlike my last two posts where I just kind of vanished after publishing.
2 Comments
Insightful✨
ReplyDeleteGreat
ReplyDelete