Sourav Mahato

One thing that backend slowly taught me... When I started learning backend, my focus was always on the happy path. I used to think, user sends the correct data, backend processes it, response goes back. If that flow was working, I felt like "okay, it's done." But with time I realized that's only one side of the story. Now, whenever I build something, I spend more time thinking about the unhappy path. What if the data is wrong? What if the user doesn't send a required field?

As a fresher stepping into software development, I initially focused on languages, frameworks, and tutorials, building small projects just for practice. After months of learning the development cycle, trying, failing, fixing, and sometimes feeling frustrated but continuing, one project changed how I think about software. It made me realize development is not only about code, but about people, problems, and perspective.

While working on the frontend of my project, I used shadcn/ui, and it has been a great experience. The components are clean, stable, and highly customizable. Since itโ€™s built on top of Radix UI and integrates well with Lucide icons, it provides both accessibility and flexibility out of the box. Because of this, I spent less time building basic UI components from scratch and could focus more on improving UX, responsiveness, and overall design quality using CSS.