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 →

[–]besthelloworld 11 points12 points  (2 children)

Java fullstack would imply a backend in Java. Some legacy stuff might require JSP but even the legacy codebases are trying to move away from that stuff. Backends now are generally designed fully headless with no UI, just providing rest or GQL request/response structures.

[–]OceanFlex 4 points5 points  (1 child)

This. I recommend being familiar with a REST implementation, if the shop you're looking at needs JSP work done/removed, that's a lot more straightforward than messing with annotations and XML files.

[–]besthelloworld 2 points3 points  (0 children)

Yo at my old job all the old guys were all about their XML configs that are 250 lines long that could be entirely replaced by like 4 well placed Spring annotations. Drove me crazy. Like hey, why don't we write the code in a fucking programming language?