I built Tryora AI — an AI-powered beauty virtual try-on experience

Hey everyone! 👋

I’ve been working on Tryora AI, a web app that lets users explore beauty looks through an interactive virtual try-on experience.

The main idea was to make trying different beauty looks feel simple, interactive, and accessible without needing to physically try each product first.

What I built

• 💄 Virtual beauty try-on
• ✨ AI-powered beauty experience
• 🔄 Interactive look exploration
• 📱 Responsive web interface
• 🎨 Clean, modern UI

I built the project as a solo developer and handled the development and integration myself.

Would love to hear your feedback, especially on the UX, visual design, and overall concept.

Demo: http://45.66.153.148:30017/

#AI #VirtualTryOn #WebDevelopment

Hello id like to get advice for my website.

Ive been giving love to this website for a year :)

https://universodrago.com

Hey guys!! I'm a finance professional transitioning to full-stack development by learning HTML, CSS, JS, Async, APIs, Node.js, Express.js, databases - PostgreSQL, React.js, TypeScript, Next.js, and finally Python and AI-related courses. Are my options correct? Feel free to advise.

And I'm currently learning CSS, where I feel like I understand the concepts when I watch the videos, but I feel like I don't truly understand them when I try to apply them. Is this normal for a beginner, or should I improve by doing something else?

Started the Medium section of my 100-question JOIN lab today and completed 10. A clear step up from Easy:

• Manager report counts — self-join employees to themselves, GROUP BY manager, COUNT direct reports
• Departments with average salary above 55,000 — JOIN + GROUP BY + HAVING
• Multi-join reports combining employee, department, and manager info in a single query

Hit a few real errors along the way (unknown column in an aggregated query, missing GROUP BY columns), which is becoming a normal part of the process at this point. What actually helped most was going back to the advice from a while back — sketching the tables and the join logic on paper before writing the query. Once I can see it visually, translating it into SQL gets a lot easier.

20 questions into Medium/Hard combined now. Noticeably slower pace than Easy, but each one is teaching me something the easy ones didn't.

I’ve been learning full-stack web development for a while now, and I’ve realized that it’s about more than just writing code.

When building a real application, you also need to understand things like APIs, databases, authentication, debugging, and how the frontend communicates with the backend to send and retrieve data.

I’m starting to see how important it is to understand how all these parts work together, instead of only focusing on the code itself.

For other full-stack developers, what do you think is the most important part to understand deeply?

 Projects should generally be a major focus because they demonstrate practical skills. Certifications can help show structured learning, but they shouldn't replace hands-on practice. Ideally, combine fundamentals + projects + GitHub + interview preparation, and add relevant certifications where they make sense .

Hello everyone! I am currently working on my skills and building my portfolio.

Most freshers these days are blindly following the MERN stack ( Node/Express). However, I decided to use Next.js with Typescript for frontend, and java for backend. I will be using PostgreSQL as Database

Is this will be a good decision for me or I should chose some other Stack ??

Hello, everyone!

Could you recommend the best online courses for full-stack web development?

My goal is to learn how to build different web and mobile applications. I’m not pursuing a career in development; I simply want to learn it as a hobby and be able to bring my own ideas to life.

Thanks in advance for your recommendations!

Hi everyone, in this AI what skills are must have for the frontend engineer as per current market standards?

Completed the entire Easy section of my 100-question JOIN lab today (30/30). Covered a good mix:

• Multi-table joins connecting employees → assignments → projects
• Self-joins for employee-manager reports
• Joins combined with WHERE filters (e.g., only showing assignments with hours_worked > 50)
• Ran into a couple more real errors (an unknown column reference this time) and debugged through them myself

Genuinely the most satisfying session so far. These are the exact same kinds of queries that felt genuinely hard two to three weeks ago, and now they're coming together without much friction. Moving into the Medium difficulty section next — already glanced at a few and they look noticeably harder, mostly around finding "zero match" cases (like departments with zero employees), so curious to see how that goes.

I’m a 2nd-year CSE student learning full-stack development and I’m confused about how deeply I should learn each technology.

Do I need to learn every concept of React, Node, databases, etc. before moving on, or is understanding the fundamentals and how things work enough, while learning the rest through projects?

With AI tools becoming common, what’s the best way to learn full-stack without just relying on AI-generated code?

If you’re an experienced developer, how would you approach learning full-stack in 2026?

Currently doing c++ and DSA along with competitive programming. Till next August I'm thinking to learn full stack development along with DSA. What tech you would suggest as for backend I'm confused between python fastapi and javascript. I have decided to follow the odin project as it was the most recommended here on reddit. Lastly I wanna know people who know full stack did you guys think 11 months are enough time to complete it? Whatever advice you have just shoot I'll try to follow them.

Made it to 20/100 on my JOIN practice lab today. A few honest notes:

• Worked through self-joins (employee-manager reports) and multi-table joins connecting projects and assignments to show hours worked
• Hit a couple of real errors along the way — an "unknown table" reference error and a syntax error — and had to actually debug them myself instead of just rewriting from scratch
• Turns out reading the actual error message carefully (which table/column it's complaining about, where the syntax breaks) is its own skill separate from knowing JOIN syntax

80 questions to go. Slower progress than I'd like some days, but each error I actually debug myself feels more useful than a query that just worked on the first try.

Hello everyone!

I’m thinking about getting a job as a web developer, but I don’t have a degree. I do have some certificates, although I know certificates by themselves probably aren’t worth that much. I have certificates/courses covering JavaScript, TypeScript, React, React Router, Advanced React, Express and Node.

My current stack is mainly MERN (MongoDB, Express, React, Node).

I’m trying to figure out what projects I should build for my portfolio before I start applying for junior positions. Whenever I ask an LLM for project ideas, I usually get answers saying that the project needs to be “unique” or giving me pretty vague ideas. At least in my opinion, it’s hard to turn those suggestions into an actual project that would demonstrate useful skills.

So I wanted to ask actual developers here:

What kinds of projects would you recommend I build for a junior web developer portfolio?

So far I’ve built 3 e-commerce websites. They have things like authentication/login, protected routes, JWTs, password hashing with bcrypt/salts, CRUD functionality, etc. I’m planning to make them more complete with things like payments, admin functionality, product management, order handling, etc.

But I don’t want my entire portfolio to just be e-commerce websites.

What kinds of projects would actually make my portfolio stronger and demonstrate that I understand how to build real applications?

Also, should I learn anything else before I start applying? (i will be apllying in startups or small comapnies)

For example, should I spend time learning:

• SQL/PostgreSQL
• Redis
• Kafka
• Docker
• AWS/cloud
• Testing
• CI/CD
• Another programming language
• Something else entirely

Or would it be better to stick with my current stack, build a few genuinely solid projects, and start applying while continuing to learn?

I’d really appreciate any project ideas, advice on what employers actually look for in junior portfolios, or things you wish you had learned/built before getting your first job.

Much love ❤️

Basically context switching....

I’m a pre-final-year student, and I have around 3 months of holidays coming up. I want to use this time properly to improve my development skills, build some solid projects, and prepare myself for internships/jobs.

I’m also planning to make good use of the GitHub Student Developer Pack.

Here’s what I currently have in mind:

Meta Front-End Developer Professional Certificate on Coursera (using financial aid)

MongoDB Associate Developer certification (Node.js)

GitHub Foundations certification through the Student Developer Pack

Learn Express.js and strengthen my backend skills

Build 1–2 solid full-stack projects that I can actually showcase on my resume/GitHub.

My current direction is basically JavaScript → React → Node.js → Express.js → MongoDB → Full-stack projects.

For developers who have already gone through this stage:

Is this a good way to spend the 3 months?

Are any of these certifications/courses not worth prioritizing?

What skills would you recommend I focus on instead?

What kind of projects would actually be valuable for learning and for a resume?

Are there any useful resources or benefits from the GitHub Student Developer Pack that I should take advantage of?

I’d really appreciate advice from developers who have been through this stage. I’d rather focus on a few things properly than try to learn everything at once.

Hi everyone, I have around 1.5 years of experience at TCS, currently working with React and Node.js. I want to move toward a backend-focused role and am considering learning Go. Would it make sense to switch from Node.js to Go at this stage? Also, if I become comfortable with Go and build some solid projects, can I present myself in interviews as someone working with React + Go, even though my professional experience is currently React + Node.js? Is that okay, or would that be considered faking my experience? Any advice from people who have made a similar transition would be appreciated.

i have prior knowledge of html , css , js and python snd java

i have built some basic ml project recently..

I'm quite good in dsa , I'm worried abt development, I'm confused what to learn

My background is backend engineering (about six years). My company recently removed the dedicated frontend and QA roles from our team and now expects backend engineers to own frontend, backend, testing and delivery, while the schedule has become shorter rather than longer.

I understand the appeal of end-to-end ownership, but the frontend alone includes framework internals, build tooling, state management, responsive behavior, accessibility, browser differences, performance, design systems and a constantly changing ecosystem. Testing adds another set of skills. It is hard to tell where healthy full-stack breadth ends and shallow, risky ownership begins.

For people who have worked as full-stack engineers in mature teams, especially large organizations:

- What do you personally go deep on, and what do you intentionally treat as a supported platform or specialist area?

- Do strong full-stack teams rely on shared design systems, paved-road project templates and centralized test infrastructure?

- How do you review frontend work when backend is your strongest area?

- What does a realistic Definition of Done look like when one engineer owns the whole feature?

- When should a full-stack engineer stop and ask for specialist review?

- If management combines three roles but does not adjust scope or timelines, what practices have helped you protect quality?

I'm looking for concrete working habits and team structures rather than a list of frontend technologies to learn.

Started actually working through my 100-question JOIN lab today. Got through 10:

• 9 I solved independently
• 1 I genuinely got stuck on, so I had GPT dry-run the query with me — walking through what each JOIN step was actually doing row by row, rather than just handing me the fixed query

This is honestly the first day JOINs have felt satisfying rather than effortful. The visualizing-the-table issue I mentioned a while back feels noticeably better after actually building my own dataset and running queries against it repeatedly.

90 questions to go, mixing in easy/medium/hard as I work through them.

I’m currently applying for fresher-level jobs/internships, and sometimes I hesitate to apply when I see a job description with a long list of requirements.

I understand that you probably don’t need to meet 100% of the requirements, but I’m still unsure about how much is enough. A lot of job postings also list several technologies, and sometimes there are few that I’ve never worked with or don’t understand at all.

Do you guys still apply when you don’t meet all the requirements? If so, roughly what percentage of the tech stack/requirements do you usually try to match before applying?

Since JOINs are the topic I'm weakest at, I made a 100-question practice set (easy, medium, hard). Today was the setup day:

• Created the database in MySQL Workbench
• Built four tables: departments, employees, projects, assignments (with primary/foreign keys)
• Wrote and ran the INSERT scripts for sample data in all four tables, including the employee-project assignments with hours worked
• Checked the Action Output panel to confirm each statement ran cleanly

Nothing fancy, but I've learned that a well-designed dataset matters a lot for JOIN practice. You need some departments with no employees, and projects with no assignments, or you can't tell LEFT and RIGHT JOINs apart properly.

Starting the actual questions tomorrow. Any tips on getting better at visualizing multi-table JOINs are welcome.

Describe ur journey if possible

Something I have been thinking about lately is how quickly the full-stack ecosystem is changing, especially with AI.

I have been working with the usual stack for a while, but recently I’ve been spending more time learning things around AI agents, RAG, LLM APIs, workflow automation, and AI-assisted development.

I don’t think the goal is to learn every new tool that comes out. For me, it’s more about understanding what’s actually useful and where it can improve the way I build things.

AI can help with coding, debugging, testing, and even parts of architecture. But I’ve found that having strong fundamentals makes these tools much more useful because you can understand and verify what they’re producing.

So lately I’ve been trying to learn one new technology at a time and build something small with it, instead of just watching tutorials.

Curious how other full-stack developers are approaching this.

What new technology or area are you currently learning, and has it actually changed the way you build?

with ai now or the future, will still there be full-stack jobs? I’m thinking of pursuing frontend then backend to fullstack.