Hey, just joined the community and Hello.
As a junior/newbie what do i need more asking advice form senior's and thanks...
So my i just recently completed my (MCA) created a project to present in hiring.
using (MERN) Stack and cloud storage (cloudinary).i tried to do most of the thinks i thought with proper (Git) history maintained and planning to deploy it before interview i used postman for endpoints testing.
Core Features
- Authentication & Authorization
- Book/Resource Management
- User Management
- Admin Dashboard with Real-Time Stats
- Auto Cache Refresh System (stale Data)
- Clean Component-Based Architecture
Security
- JWT Authentication (Access + Expiry tokens)
- bcrypt Password Hashing with Salt
- Verification Token for Sensitive Actions (Delete)
Performance & UX
- React Query for Smart Caching
- Global Cache Manager (Auto Invalidation)
- Optimized API Layer with Interceptors
- Responsive UI/UX Across Devices
Top comments (4)
Hi Tanish,
My impression here is that you are trying to jam way too much into the application. This leads to a few red flags:
First is low level implementation of Auth. Trying to manage authentication yourself is very risky, and I highly recommend you learn to use other OAuth2 providers. If you are going to offer username password style auth you become responsible for a bunch of complexity that you can avoid by using other providers. Using Google OAuth eliminates the risk of exposing user passwords. Hashing and salting is minimal if you do go down this road, but ideally just avoid this aspect if possible.
Second - you appear to be using multiple performance technologies in a small project. There is an anti-pattern called Premature Optimization where the solution becomes more complex than really needed in anticipation of performance issues. Ideally leave performance improvements until you understand where the bottlenecks are. For example, you don't really need a CDN for a basic low volume website.
The admin dashboard for stats might be better served by a separate app, as this sounds more operational. The principle here is separation of concerns; no need to include a operational tool in the user facing code. If you did separate them already my apologies.
Hey, I know its hard out there right now. Getting a foot in the door can be hard, but if you are showing you are passionate about code, care about quality, and understand risks such as security issues it will really help. Also; don't try to be expert at everything out of the gate. Better to know fewer technologies well.
All the best, Peter
thanks for advice but as i mentioned i am going to show this project in interview
so that's my logic behind it to showcase i know things instead of explaining verbally if i can show i know something understand and how it works ....
and YES i created ( 3-seperate ) folders for my project
currently i want to add bunch of stuff like (pagination, search, filters) etc, and yes right now i am storing JWT in local-storage for now but i am also thinking they can ask why not cookies instead and other stuff.
well thanks for advice 👍
If you have it deployed drop a line with the URL.
I haven't deployed it yet but when my internship ends then deploy it...