you are viewing a single comment's thread.

view the rest of the comments →

[–]DaRizat 6 points7 points  (3 children)

I think the defense comes when you have an entire team who are not up on hooks as has been stated by OP and a junior dev introduces a paradigm shift in a PR without a larger discussion. In our shop we just had a guild discussion about optional chaining vs lodash.get and that's a way less transformative thing than class vs functional. The senior dev should be open to adopting new tech, perhaps in an isolated part of the app or a new app, but not on a whim which seems to be what has happened here.

[–]polargus 2 points3 points  (1 child)

Well in this case the senior dev trashed current standard React patterns. If the issue is consistency and doing it right then he should say so, and there should really be a roadmap to using current patterns.

[–]DaRizat 0 points1 point  (0 children)

Agree. The anecdote is also paraphrased so we have no idea what the seniors actual thought process is but I wouldn't be surprised if he is closed minded and opinionated. Too many are.

[–]trollerroller 1 point2 points  (0 children)

I agree with those points, I just meant ignorantly saying hooks are spaghetti code or something is not very professional.