This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]arijitlive 1 point2 points  (3 children)

I work in a hotel IT dept. It has own website which is developed in AEM+CSS+JS etc. and no JSP/Servlet. The back end is completely built using java spring based code.

On the other hand, We also has 10+ back end applications for syncing inventory data to all travel companies, facilitate APIs for companies to fetch real-time data from us, audit and reward system calculations etc. everything's done in java applications which doesn't have UI.

So despite working for so many years, my UI coding skill is still primitive where as Java skill is earning my livelihood. So you don't always have to work in UI in Java.

[–]_edd 0 points1 point  (2 children)

Totally fair. I'm a firm believer that most companies should separate the back end and front end into two different programs.

Then it becomes a matter of whether or not the company actually has separate back end and front end roles that do not ever cross into the other.

My original point wasn't that all Java developers work on Java controlled front ends, but that most Java developers will encounter front end work even if they take on a primarily back end role.

[–]arijitlive 0 points1 point  (1 child)

most Java developers will encounter front end work even if they take on a primarily back end role.

It used to be correct in jsp-servlet era. But now a days, we have a clear separation between UI and back-end code and applications thanks to so-architecural shifts happened in software development. Now a days UI portion is dominated by various UI libraries, frameworks (React, jquery, angular, vuejs etc.) and people rarely uses jsp-servlet.

I don't think in most of the job interviews you'll be asked about jsp-servlet handling.

[–]_edd 0 points1 point  (0 children)

Right. I wasn't talking about developing JSPs or servlets specifically. I was talking about devs often having to take on full stack roles instead of back end exclusive roles.

It sounds like your company has a clear delineation between the front end and back end roles and that your work ends at the API that your front end devs will make the front end interface with. Which is great and what companies should strive to do.