6 ms·

Your last point is a cause of some apprehension for me. In the team I'm currently working with one of my coworkers calls himself a React Developer, and my exper

by II-V-I 6y ago

Your last point is a cause of some apprehension for me. In the team I'm currently working with one of my coworkers calls himself a React Developer, and my experience has been that anytime an issue arises that may not be specific to React, this person's ability to problem solve significantly diminishes. I've seen it in a couple of other individuals as well, and I feel it's becoming more widespread, though I hope I'm wrong. In these instances, I see the framework existing both in the code as well as the mind, and operating outside of it is often a leap too far.

JackMorgan 6y ago
Personally, I'm super wary of any ____ developer. It's a fixed (vs growth) mindset that tells me they are specialists. I think specialists are best to be consulted by generalists, but not trusted with larger decisions outside their scope.
otachack 6y ago
Maybe bring it up to him with constructive criticism? Tell him the wind tends to change direction and one shouldn't typecast themselves in this field.
- II-V-I 6y ago
  I agree. Though this person can be a bit touchy when constructive criticism is aimed at them, this would most likely be beneficial for them, and also the team, in the medium/long run.
dehrmann 6y ago
This is usually a smell that the person is competent at what they do, but doesn't know what's going on under the hood. Funny enough, I'd rather work with someone who doesn't know the specific technology, but knows what the language was built on top of, because they'll have a better intuition for how it actually works and be able to learn it relatively quickly.
- II-V-I 6y ago
  I'd rather work with someone like that, too. All is well and good when one can crank out React components, but if that same person doesn't know how to find, for example, the tag name of a element from an event handler, a little red flag goes up for me, and as you said, probably doesn't know a great deal about what's going on under the hood.
  - deleted 6y ago
    [deleted]
sngz 6y ago
> and my experience has been that anytime an issue arises that may not be specific to React, this person's ability to problem solve significantly diminishes. this has been my experience too, I'm a full stack engineer playing a devops role right now on a greenfield govt project. Getting our CI/CD pipeline going within our environment constraints with react has been a pain in the ass. Every time something goes wrong the front end dev just kinda throws his hands up and basically tells me its my problem. I ended up having to go through all the issues opened on github to find solutions and implement them myself. I'm no javascript expert but to me the solutions seem to be super hacky when I've found other frameworks out there that handle these things out the box or more gracefully. I was on a project supporting legacy code for a long time before this, and was quite looking forward to working with newer js frameworks but this left a sour taste in my mouth. And I already had a bad impression of react prior. I might look into pushing for some of the alternate frameworks out there.
- II-V-I 6y ago
  Oof. Sorry to hear the FE dev gives up like that. You may become a JS expert if that carries on. > the solutions seem to be super hacky when I've found other frameworks out there that handle these things out the box or more gracefully. I'm curious to hear what alternative frameworks handled these things better? The only one I've used recently, other than React, is Vue.
  - sngz 6y ago
    So the issue I'm referring to is this, which has been open since 2017 https://github.com/facebook/create-react-app/issues/2353 https://github.com/facebook/create-react-app/issues/2353 There's a slew of workarounds offered in that github issue, most people (including another team in my org) opted to just rebuild the app every time a docker container is created which kind of defeats one of the major pros of using docker IMO. I ultimately ended up forking off this repository and customizing it to my needs https://github.com/beam-australia/react-env https://github.com/beam-australia/react-env that solution in itself is very hacky. as far as I know, vue doesn't have this feature either but I think next.js and nuxt.js does.

by II-V-I 6y ago

JackMorgan 6y ago

Personally, I'm super wary of any ____ developer. It's a fixed (vs growth) mindset that tells me they are specialists. I think specialists are best to be consulted by generalists, but not trusted with larger decisions outside their scope.

otachack 6y ago

Maybe bring it up to him with constructive criticism? Tell him the wind tends to change direction and one shouldn't typecast themselves in this field.

II-V-I 6y ago
I agree. Though this person can be a bit touchy when constructive criticism is aimed at them, this would most likely be beneficial for them, and also the team, in the medium/long run.

dehrmann 6y ago

This is usually a smell that the person is competent at what they do, but doesn't know what's going on under the hood. Funny enough, I'd rather work with someone who doesn't know the specific technology, but knows what the language was built on top of, because they'll have a better intuition for how it actually works and be able to learn it relatively quickly.

II-V-I 6y ago
I'd rather work with someone like that, too. All is well and good when one can crank out React components, but if that same person doesn't know how to find, for example, the tag name of a element from an event handler, a little red flag goes up for me, and as you said, probably doesn't know a great deal about what's going on under the hood.
- deleted 6y ago
  [deleted]

sngz 6y ago

> and my experience has been that anytime an issue arises that may not be specific to React, this person's ability to problem solve significantly diminishes. this has been my experience too, I'm a full stack engineer playing a devops role right now on a greenfield govt project. Getting our CI/CD pipeline going within our environment constraints with react has been a pain in the ass. Every time something goes wrong the front end dev just kinda throws his hands up and basically tells me its my problem. I ended up having to go through all the issues opened on github to find solutions and implement them myself. I'm no javascript expert but to me the solutions seem to be super hacky when I've found other frameworks out there that handle these things out the box or more gracefully. I was on a project supporting legacy code for a long time before this, and was quite looking forward to working with newer js frameworks but this left a sour taste in my mouth. And I already had a bad impression of react prior. I might look into pushing for some of the alternate frameworks out there.

II-V-I 6y ago
Oof. Sorry to hear the FE dev gives up like that. You may become a JS expert if that carries on. > the solutions seem to be super hacky when I've found other frameworks out there that handle these things out the box or more gracefully. I'm curious to hear what alternative frameworks handled these things better? The only one I've used recently, other than React, is Vue.
- sngz 6y ago
  So the issue I'm referring to is this, which has been open since 2017 https://github.com/facebook/create-react-app/issues/2353 https://github.com/facebook/create-react-app/issues/2353 There's a slew of workarounds offered in that github issue, most people (including another team in my org) opted to just rebuild the app every time a docker container is created which kind of defeats one of the major pros of using docker IMO. I ultimately ended up forking off this repository and customizing it to my needs https://github.com/beam-australia/react-env https://github.com/beam-australia/react-env that solution in itself is very hacky. as far as I know, vue doesn't have this feature either but I think next.js and nuxt.js does.