Win a copy of Fixing your Scrum this week in the Agile forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Rob Spoor
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Junilu Lacar
  • Tim Cooke
Saloon Keepers:
  • Tim Holloway
  • Piet Souris
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
  • Frits Walraven
  • Himai Minh

Basic tech stack for backend developer

Ranch Hand
Posts: 58
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

I know there are a lot of guys who work as a professional Java developer more than 3 years and can possibly help me with next question.

But let me go back in time a bit firstly.
When I was working on my previous job (analyst position, 7 years experience), new guy in the office asked me next question: what development direction should he choose and what knowledge is valued today in a particular industry. I think it's the best question that anyone could ever ask at the new job. People, who work there for a long time definitely know actual tech stack and today's trends. Professionals can even sort it in a value (most valuable and best to start from) order without any difficulties. That's an impossible task for a newbie.

As I can see, there is some basis in Java:
1) Core: OOP, I/O, multithreading, exceptions handling and so forth..
2) Design Patterns
3) Algorithms
4) SQL
5) Some basic –°omputer Science

And aside from that there is something that is valued TODAY. Something that employers are looking for.
I'm a fan of the idea that any novice should be focused on main things. To find job is the first priority for me and then I can totally focuse on professional improvement.

So, now directly to the questions. I'm not a big fan of a frontend (I know it's a must have knowledge, but everything has it's time), so I'm asking as a potential backend Java developer. What do you think is a next step for a newbie who learnt basics and want to be "in demand" on today's market? If it's Spring, what exactly to start with? What's after Spring? Where would be the point for me to say to myself "stop now, you learnt something, try to get the job and be practicing what you learnt at the same time".

I read a lot of articles, but most of them are just a list of books to read one by one. I don't think it's a good practice. Without working experience it would be just a waste of time for 75% of information.

Thanks in advance for your answers.
Java Cowboy
Posts: 16084
Android Scala IntelliJ IDE Spring Java
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
There is no objective or universally correct answer to your questions. One thing you could do is look around at companies in your region who are looking for back-end Java developers, and find out what exactly they are looking for.

In my opinion, the two most important technologies a Java back-end developer should know beyond the basics that you already mentioned yourself are Java EE and Spring. But both of these are huge areas, with many different parts. Don't expect to learn either Java EE or Spring in a matter of weeks; learning these will keep you busy for months or even years.

A good place to start with Java EE is Oracle's Java EE Tutorial.

For Spring, take a look at the Spring website, especially the Spring guides.
Consider Paul's rocket mass heater.
    Bookmark Topic Watch Topic
  • New Topic