DEV Community

Discussion on: Is front-end development having an identity crisis?

Collapse
 
davelnewton profile image
Dave Newton

Whether or not something like functional programming is an expectation depends on the FE position in question, e.g., if my FE is built in Elm, it's an expectation, because it's likely I don't have the time to train up somebody in FP.

Regarding the position requiring Java and MongoDB, that's not an FE position, it's full stack, if they're expected to do anything other than interop with the non-FE techs. Calling it an FE position doesn't make it one.

You're also limiting this to web development, which while the primary consumer of "front end" development, isn't the only one, e.g., there are new apps where there might be a Swing, JavaFX, or whatever the MS equivalent is. FE just means "immediately user-facing", which isn't only the web. Obviously that's a very small portion of FE jobs these days--just sayin'.

The examples shown seem to boil down to labeling problems, not definition problems.

Collapse
 
assaultoustudios profile image
Vernon Joyce • Edited

So yes, primarily my point is really that the labels are wrong (I.e the job titles). I’m completely aware of the landscape as it currently stands, and I’m a realist, don’t get me wrong. This is exactly the case for the Java role as it should have been labeled full-stack as opposed to FED.

But I’ll give you a very practical example.

I know plenty of front-end developers who work in agencies. At a stretch they might use some Angular but they are mostly responsible for building interactive web experiences for brands - which is very different to building data driven web applications. If 99% of FED roles ask for some sort of back end or Reaxt experience where would that leave them?

Perhaps the onus is on them to upskill and keep up with tech, but if you work full time that’s often very hard to do.

I do concur that my experience is completely based on web so perhaps my opinion is biased.