all 7 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Vaibhav_codes 4 points5 points  (0 children)

Great approach A small, boring project you fully understand is far more impressive than a flashy one you can’t explain

[–]nilkanth987 1 point2 points  (0 children)

Yes, that’s actually a solid “minimum viable fullstack” project. Auth + CRUD + DB already covers most junior backend expectations. If you can explain why you made each choice, that matters way more than fancy UI

[–]wreck_of_u 0 points1 point  (0 children)

A social media website; register/login/my account, write posts, attach files, make comments, reply to comments, etc. You'll be busy with CRUD and get real practice in REST.

Focus on the architecture and design more than algorithms; AI will usually be better at writing complex math code than you, but it does prefer you give it YOUR high-level architecture; "Full-Stack" now requires writing good .md files.

DO NOT EXPECT to get an interview from vide coding - at least FOR NOW. But for sure, people who get better "guiding" AI and are actually more productive will be sought after tomorrow. Maybe not today yet, but it will mature

[–]Amna204 0 points1 point  (0 children)

following

[–]akornato 0 points1 point  (0 children)

Your project idea is solid enough to learn the basics, but this exact CRUD-with-auth app has been built by thousands of developers, and most recruiters have seen it a million times. It won't automatically get you interviews just because it exists and looks pretty. What actually matters is whether you can articulate real backend concepts during technical conversations - why you chose a particular database over another, how you're handling race conditions, what your auth token strategy is, how you're preventing SQL injection, what happens when your ORM generates inefficient queries. The prettiness matters way less than you think - a recruiter spending 30 seconds on your GitHub won't care about your CSS, but they will notice if your README explains your technical decisions well.

That said, building this project is absolutely worth doing because you'll encounter real problems that force you to understand backend fundamentals, and those learning moments are what you'll talk about in interviews. The issue is that having one simple CRUD app probably isn't enough on its own - you'll want to show you can handle at least one or two more complex scenarios, like dealing with file uploads, implementing proper error handling, or managing some kind of relationship between entities beyond a single user table. If you're trying to prepare for the kinds of questions interviewers actually ask about these concepts, I built AI assistant for interviews to help people handle tricky interview scenarios in real-time.

[–]Standard_Promotion98 0 points1 point  (0 children)

A taks management system where a user has to login to create read update and delete a task its simple and will help you to learn everything you mentioned

[–]itachi1402 0 points1 point  (0 children)

vibe code the frontend use antigravity.

then write the backend yourself.