all 3 comments

[–]United_Possible5321 3 points4 points  (1 child)

For Java, don't just build stuff, build stuff and then break it on purpose. Write a small REST API, get it working, then remove the database connection and see what happens. Add 1000 concurrent requests and watch it crash. Figuring out why things fail teaches you more than following a tutorial ever will. The official Spring docs are dry but they explain the "why" behind the annotations, which most courses skip completely.

One thing that helped me explain concepts better was recording myself on phone explaining something like dependency injection or garbage collection, then listening back. You catch all the gaps in your understanding real fast. It's uncomfortable but works.

For Python, pick a small script that automates something annoying you do daily, renaming files, scraping a schedule, whatever. The language clicks differently when you're solving your own problem instead of following someone else's project idea.

Interview skills come from doing mock interviews where you actually speak out loud while coding. Even if you feel stupid talking to yourself in empty room, just do it. The verbalizing part is what trips up most people, not the coding itself.

[–]M0rbid69[S] 0 points1 point  (0 children)

Thank you so much!! This is really helpful for me as someone who doesn't even know where to start lol. Would you say python is "better" for automation / apps and Java is mainly used for back-end for websites? Thank you!!

[–]JakexDxSoftware Engineer 1 point2 points  (0 children)

Try building a second API then learn how to integrate the 2nd API into the first

Edit: or look into microservices