Viewing a single comment thread. View all comments

debunk_this_12 t1_j8dd2io wrote

Reply to comment by bman1014 in [OC] Developer jobs popularity evolution on google trends: What obstacles to change career from full stack to front end developer? by cepegma

Wouldnt a full stack dev build front ends? That’s what that means… they build the front and backend🙃

5

gizzardgullet t1_j8e7e7c wrote

A fullstack developer must disavow server side developing to become a front end developer. A good psychiatrist should be able to erase the programmer's memories of back end development using cognitive behavioral therapy. Electroshock therapy is often used if the programmer relapses and starts coding back end solutions again.

6

What-Fries-Beneath t1_j8fi2il wrote

People go in the other direction because front end development is challenging and fun, but absolutely HORRIBLE work to do for other people on teams where everyone else is late/lazy and you have to constantly pick up the slack: for less money, and far less respect.

Edit: It's important to mention just how awful it is to have everyone tell you how "easy" and "simple" things are because they're so familiar with the output. If you want to get stabbed come say something like "it's just a calendar" to me in person.

- Front end dev who "retired" to mathy stuff.

2

cepegma OP t1_j8h5fyx wrote

But still, what are the main difficulties when changing a career path from full stack to front dev? or it's a relatively straightforward change? Have you experienced this kind of career change?

1

What-Fries-Beneath t1_j8iskyu wrote

Technically full stack includes front end. So really it all depends on how well someone actually understands that layer. Like I know some dev-ops and some ml-ops, but to do dedicated either I'd need a fair bit of work.

Ultimately it depends on the job requirements. Some places you'd be fine just knowing react, css, typescript, etc. No matter your title if you stay on the surface like that you stay junior.

Dedicated senior front end should really understand how browsers actually work. Should be able to build various libraries and frameworks using raw js, but know to avoid that if at all possible. Should have worked with at least a few ui-frameworks. Should understand workers, sockets, events, shadow dom, css build as part of or separate from webpack build, webpack build, canvas, various common patterns for handling async like observables/promises/acid, functional and OOP, render cycles, debouncing, various local storage/cookie based ish, typescript, node, etc.

Really the main thing is about learning how to handle complex, non-linear state. Everything I mentioned is about state, and most apps need to be rearchitected from scratch because the designs are different. Unless you're working on boring stuff hahah.

Then there's all the design and UX stuff one should be at least a little familiar with.

And if you want to do web specifically there's a bunch of ish for that. You can build internal apps with the above.

>Have you experienced this kind of career change?

Hmm well I started out a barely trained full stack dev, then went nearly dedicated front end for a few years, so kinda? Front end is more complicated and takes constant work to stay on top of. That's what makes it fun. And also terrible and I'm never going back no matter how much people keep asking irl.

1