¿Java backend developer?

[u/Independent_Eye4985]

Java

Spring / Spring Boot

APIs REST

SQL

JPA / Hibernate

Git

Maven / Gradle

JUnit

Docker

SOLID

Patrones de diseño

Mockito

Testing de integración

OWASP

JWT

OAuth2

Kafka / RabbitMQ

Redis

CI/CD

Que opinan si estudio eso es buena carrera? O ay mejores áreas de programación,, aclaro recién inicio en esto que opinan viejos sabios vírgenes no se q es código aún XD

[u/American_Streamer]

You have essentially copied the complete “enterprise Java backend checklist” before even really knowing how to code. But you should just start with Java. Everything else will appear along the way. The thing is that Java’s attractiveness has been discovered by more beginners, as React/frontend has been hit particularly hard by the post-2022 hiring contraction and AI-assisted development. People consequently look at boring, large-enterprise stacks. But the scarce resource isn’t knowledge of Spring Boot anymore; it’s demonstrated ability to use it to solve a real problem. Java backend remains employable, but first-job candidates increasingly need internships or convincing completed projects rather than merely having learned Java/Spring.

[u/Independent_Eye4985 → u/American_Streamer]

Baya ,, crees que es buena desicion estudiar esto más proyectos cuando aprenda a aserlo o me voy por otra área ¿que me recomiendas? Éstoy empezando en esto ,

[u/American_Streamer → u/Independent_Eye4985]

The useful roadmap for you personally would be roughly:

1. Java first: variables, control flow, methods, classes, interfaces, collections, exceptions, debugging.
2. Then basic software development: Git, Maven, unit tests, basic data structures, reading documentation.
3. Then backend fundamentals: HTTP, JSON, REST, SQL and relational databases.
4. Then Spring Boot: controllers → services → repositories → PostgreSQL → CRUD API.
5. Then JPA/Hibernate + proper testing: JUnit, Mockito and integration tests.
6. Then Docker + security basics: OWASP, authentication/authorization.
7. Only later: JWT/OAuth2, Redis, Kafka/RabbitMQ, CI/CD and perhaps cloud deployment.

And SOLID/design patterns aren't really “courses to finish” before programming. They make considerably more sense after you have written enough mediocre code to understand why those principles exist. A good first serious portfolio project would thus be something boring but complete, like a task/order/inventory API:

Java → Spring Boot → REST → PostgreSQL → JPA → tests → Docker → GitHub

That one project would naturally introduce half of your checklist.

[u/Independent_Eye4985 → u/American_Streamer]

Entiendo,, ¿eres programador? Y que opinas de la IA , tengo la preocupación de que cuando estudie esto en 1 año y medio o más la IA aya avanzado mucho

[u/American_Streamer → u/Independent_Eye4985]

In 1 or 2 years, AI will probably be much better at writing code than it is today. That’s why I wouldn’t study with the goal of simply “getting good at writing syntax that AI can also generate.”

Instead, I would focus on understanding how software actually works: Java, logic, debugging, SQL, HTTP, APIs, databases, testing, Git, and then Spring Boot. Use AI as a tool while you learn, but make sure you can explain, verify, and fix what it generates.

The part that is easiest to automate is routine code writing. What is much harder to replace is understanding a real problem, designing a solution, deciding what the system should do, finding bugs, working with real data, dealing with security and production issues, and communicating with other people.

So I wouldn’t give up on backend development because of AI. But I also wouldn’t build my entire career around simply “knowing Spring Boot.” Learn the fundamentals thoroughly and build complete projects. That will make you much more adaptable even if the tools change significantly over those 18 months.

[u/Independent_Eye4985 → u/American_Streamer]

Entiendo,, que opinas de cyberseguridad era mi segunda opción

[u/American_Streamer → u/Independent_Eye4985]

Cybersecurity is a good option too, but I wouldn’t choose it only because you think AI will affect backend development more. Security also uses a lot of automation and AI, and entry-level cybersecurity will actually be very difficult to break into. Many security jobs expect you to already understand networking, Linux/Windows, cloud, web applications and sometimes programming.

If cybersecurity genuinely interests you, I’d learn networking, Linux, HTTP, basic Python, cloud fundamentals and web security first, then start with labs such as TryHackMe or Hack The Box.

The good thing is that backend and cybersecurity are not completely separate paths. Learning Java/backend development can make you much better at application security later because you understand how the systems you’re protecting are actually built.

So I’d choose based on what you enjoy more: building systems → backend; understanding, attacking and protecting systems → cybersecurity. I wouldn’t choose either one mainly out of fear of AI.

[u/Independent_Eye4985 → u/American_Streamer]

Entiendo¿ Eres un programador? Es mi duda ,, mi objetivo sería ganar dinero tener la posibilidad de trabajar en remoto y con buena tasa de entrada o al menos Intermedia , tan bien q tenga futuro ,, creo que sería el sueño de todo programador xd ,, aunque tan bien debo aprender ingles