3

Fullstack, Frontend, Backend, Bullstack!

Honestly, times have changed. There is no frontend developer any more. I mean, don't take that as an absolute, obviously there are enough left. Or rather, they probably have never existed. But I cannot fathom how someone can claim he works only frontend, can send off an http request, receive the JSON, put it into a model object, take the model object and put it in a tree and then write logic to search through the tree...

...and at the same time cannot create an endpoint where he would receive a JSON in the backend, put it into a model and save it via ORM to the database.

Or the other way around for all the people who only do backend.

What I get is: Not knowing the language and not knowing the framework. That's why I do Play, Flask, Zend, and Vue.js, but I do not do React.

But if the need arises I am willing to learn a new framework or language.

I hate fiddling with something until it looks just right. I really hate it. But even as a backend developer you cannot escape that. Server-side rendering is not yet dead and it happens in the backend. Or the distinction is kind of mute here.

So I guess what frontend dev vs backend dev actually wants to say is: Design-focused or logic-focused coder. Why don't we use those terms. If we did we could actually connect design focused devs closer to designers and put some of that into their curriculum. But at the moment, all the frontend devs I know keep repeating that they are not professional designers.

Comments
  • 0
    I agree with you for the most part. Except that "graphic design" really is a completely different skill set. I've worked with frontend developers that are designers and at least in my experience they don't do either particularly well. That's not an insult to them, just the facts of Life. There aren't a lot of people who are capable of being genuinely good at two different jobs. It's common enough to find some who's good at one and mostly competent at the other. But that's why there's a separation between designers and frontend devs. So that both can do their jobs well instead of just getting by (theoretically at least). I think there's way more in common between frontend work and Backend work, than there is between frontend work and graphic design.

    But again I do agree with you that anyone who's actually GOOD in either role can be good in the other when it comes to frontend/Backend. As long as they have time familiarize themselves with the stack.
  • 0
    @sweetnothings I wouldn't disagree with you. I've worked as a straight React Developer. But now I'm a .Net core developer with no frontend responsibilities. As I stated, this assumes you are afforded/take the time to learn the stack. I definitely wasn't saying you can just pick up frontend skills and boom you're an expert. But there are a lot of shared fundmentals and a similar thinking process. It's entirely possible to transition between the 2.

    You can totally make a career out of just one. Doesn't mean they're a mutually exclusive skillsets without overlap.
  • 1
    @sweetnothings yeah again I'd agree. From experience those folks definitely exist. Especially with the move from classes to hooks. I'm just saying it's not impossible or unheard of. Some of it just comes down to your thought process and what you like/dislike.
  • 1
    @sweetnothings

    1. Google it, so many frontend positions. Yeah, I didn't need to rant about it if this was widely accepted.

    2. Like I said, getting the look right is a special skill. That's why I proposed to have a design focused role. But getting functionality going is exactly what backend devs are good at. Doesn't have to be pretty.

    3. Learn curve. Yeah, but you have similar learning curves for frameworks. In general, a framework is a thing that replaces work with magic. You now have to learn all this magic instead of writing it yourself. If you already know a backend framework and learn another, let's call this effort a 1. Now learning a frontend framework instead is what? A 1.3? 1.4 tops!
  • 0
    @ChaoticGoods

    I didn't say make frontend devs designers. I proposed to redraw the lines. Cut frontend devs in half. Take the design patterns - logic half and merge it with backend devs. Take the other half and merge it with designers.

    I mean, I think MS tried it. WPF applications had the frontend as XML with the thought that designers could just modify the look of the frontend in a completely different application.

    Hard to admit, but I think MS was onto something here.
Add Comment