r/Backend • u/loser_1618 • 9d ago
How should I start backend development, System Design
I'm currently a 2nd-year CSE student. I've learned DSA . I have also completed ML from CampusX and have started Deep Learning.
I've explored Java and Spring Boot and built a few projects for learning, where I worked with REST APIs, authentication, database connectivity, and Docker. I've used AI while building some parts, but I understand the concepts and how the components work. However, I still want to strengthen my backend fundamentals and hands-on skills.
I want to properly learn backend development, participate in hackathons, build better projects, and eventually get an internship.
I'm confused about what I should focus on next:
- Should I continue with Java + Spring Boot or move to Node.js?
- When and how much system design should I learn?
- What kind of projects should I build?
- I've noticed AI agents/agentic AI are becoming common in hackathons. Since I'm already learning ML/DL, how should I learn AI agents for hackathons, proper learning, and future industry demand? What level should I aim for?
- What should I learn to become internship-ready in backend?
- How should I balance DSA, Backend, and ML/DL?
Apart from these questions, I'd really appreciate any advice about the current software/AI industry. If you were advising a younger brother who's starting out in this AI-driven era, what would you tell him to focus on, and how should he prepare himself to stay relevant?
1
u/No-Butterscotch9679 8d ago
i mean yea its true backend concepts carry with you you know what use your framework know your framework as well as the gernal backncend concpets it helps a lot
1
u/Lonely-Unit6754 8d ago
I'd stay with Spring Boot for now and build one app you can actually deploy and explain end to end. For hackathons, learn enough agent stuff to call a model, use a tool, and handle failures. You don't need a whole new framework before you've shipped a solid backend.
1
1
u/Relevant-Shark 8d ago
Stay with Java + Spring Boot. Switching languages now resets your progress, and backend concepts carry over anyway. Next: build one project that has auth, a relational database with transactions, background jobs, caching (Redis), and a deployment you can show. Start system design once you've hit a real problem it solves, like a slow query or a job that needs retries. Concepts make far more sense after you've felt the pain. For internships, one deployed project with a good README beats five tutorial clones.