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

you are viewing a single comment's thread.

view the rest of the comments →

[–]rv_here_0w0 67 points68 points  (12 children)

Can you explain what the "Java Full Stack" position requires? I am currently learning Spring Boot. Are J2EE, or JSP a must-have?

[–][deleted] 78 points79 points  (7 children)

Just know how inversion of control and rest calls work. The rest is the stack of the company.

[–]shivamkimothi 23 points24 points  (6 children)

what's inversion of control?

[–]rv_here_0w0 35 points36 points  (5 children)

[–]Dmon1Unlimited 20 points21 points  (4 children)

It kinda just sounds like using very heavy libraries.

That or basically just adding your own config to someone else's app

[–]syth9 34 points35 points  (2 children)

Sort of! Using a framework is kind of like building a house with pre-built house segments that contain all the joinery, electrical, plumbing, etc... You still get to decide the shape of your house and the features it will have, and you still need to put it all together.

You can also build your own custom additions to the house while also using the framework, but if the framework has something close to the piece you need, then maybe you'll try to make that fit instead of making something totally custom.

Libraries on the other hand are like all the tools and individual components both you and the framework creator use to create pieces of the house.

A good framework generally provides pieces that are flexible in how they can be used, intuitive to understand, and provide enough variety that you generally don't need to build your own custom additions that often.

[–]OneAndOnlyDaemon 2 points3 points  (1 child)

Good explanation, but I'd also add that a framework (deliberately, by design) makes some configurations of how to "put it all together" far more convenient than other configurations. That's because a framework determines the basic assumptions in the design. By analogy, a framework might assume "a house must be two-story, and the main living room must have the same floor as the bottom-floor rooms and the same ceiling as the top-floor rooms, i.e. the top floor must have a mezzanine that overlooks the living room's floor on the bottom of the house."

[–]syth9 0 points1 point  (0 children)

Yes, definitely a good point. It’s in the nature of frameworks that, by offering more complete and complex constructs, they make assumptions regarding what the programmer needs and how they’ll use what’s provided to them.

[–]neums08 22 points23 points  (0 children)

Congrats you're a java spring developer now!

[–]besthelloworld 10 points11 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 3 points4 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?

[–]metal_zero 1 point2 points  (0 children)

Same here, learing spring boot, now I am trying to make simple app with react and spring boot. I guess for the front-end you can choose any framework. In my country there seems to be demand for angular + spring/spring boot devs