I'm comfortable with Java and OOP, but Spring Boot feels like a whole different world. I want to build and deploy a full-stack website. Would switching to Python make that easier, and does either language matter more for internships?
Should I stick with Spring Boot or switch to Python for a full-stack site?
Answers
I'd stick with Java for a small first project. You're not just learning Spring Boot. You're also learning HTTP, databases, and how a browser talks to a server. Python won't make those parts disappear.
Start with a GET endpoint that returns JSON and a POST endpoint that accepts it. Then make a simple page that calls them. Add a database once you understand that flow, rather than trying to learn everything at once.
Reply to this answer
Python is a reasonable option if Spring's setup is getting in the way of building anything. Flask can be a smaller starting point, while Django provides more of the pieces for a full website. A quick prototype might be easier to get going there.
That said, knowing Python syntax in a few days isn't the same as knowing a web framework. You'll still have to learn how requests, data storage, and deployment fit together.
Reply to this answer
For internships, check the listings you're interested in rather than assuming one language wins everywhere. A project you can explain is useful too. Be ready to talk through what you built, how the frontend and backend communicate, and what you'd improve.
Reply to this answer
The frustrating part of Spring is that a lot happens behind annotations and framework configuration. If you can't follow the program flow, slow down and find out what creates your controller and calls its methods. Sticking with it can be worthwhile, but treating those pieces as magic can make debugging rough.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Roveni-9q:
How can I make Spring less confusing? Tutorials have been hard to follow.
Morlix-7q:
Try building one endpoint without a database first. Trace the request from the controller to the response, and look up each annotation you use instead of copying a whole project.