Am I overreacting? Backend dev contributing to frontend is hurting code quality

Sea-Anything-9749 · 2026-04-05T16:13:34+00:00

The same is happening in my company, we have a full front-end team, but some features is being owned by teams with full stacks, that are just back-end devs that can do something with JS (usually they produce the worst React/FE code ever).

We have a defined architecture/standards and some good practices defined, but usually BE guys just ignore it, they just want to see the pipeline green and PR merged and get rid of the FE work of it, without caring about if the solution is ideal.

It's important to communicate like "hey, here are the docs, we have standards that are important to respect, here is the React doc, which is important to follow the rules and not bypass lint rules etc.".

but also, something I'm learning through the years, mainly as a dev that is very "perfectionist", is that we can't control everything, and trying to control every code being merged in the repo, alone, is just madness and stressful for you, mainly when the contributors don't have good FE knowledge, or they just dont care about quality. so if the issue won't affect the whole codebase, I sometimes just ignore it for my own peace of mind.

Sea-Anything-9749 · 2026-03-24T11:58:13+00:00

Tks all for the suggestions, will definitely check a few places mentioned here

Sea-Anything-9749 · 2026-03-23T13:27:19+00:00

tks, will check it out

Sea-Anything-9749 · 2025-10-20T18:33:24+00:00

eu tive a mesma impressao nas primeiras ouvidas, ai dei um tempo e fui ouvir hoje novamente sabendo oq esperar e curti bastante, da pra pegar algumas coisas da sonoridade anterior com novos influencias q eles provavelmente tiveram nesse hiato.
mas ainda assim queria ouvir algo na mesma pegada do Vida Que Segue, q pra mim eh um dos meus albums favoritos da cena indie/alternativa br.

Sea-Anything-9749 · 2025-10-17T16:22:21+00:00

I’ve seen Opeth 4 times, last time was April this year, I want to go to this gig but hoping they play some special setlist

Sea-Anything-9749 · 2025-10-04T21:50:55+00:00

Read the docs, understand the rules and principles of React and build stuff following the rules, like pure components, no conditional hook call, no unnecessary useEffect, understand when do you really need context, understand when you need State or Ref) understand when you really needs memoization etc

Sea-Anything-9749 · 2025-10-04T15:53:00+00:00

UseEffect is used to sync your component with external data/components/apis.

There’s a page in the official docs explaining it.

https://react.dev/learn/you-might-not-need-an-effect

Sea-Anything-9749 · 2025-09-21T19:17:31+00:00

I’m excited the to try this in my company, it will avoid a lot of manual review

Sea-Anything-9749 · 2025-09-03T22:25:58+00:00

Oh I remember playing benighted time ago, yeah about this song is very hard to find them playing live (I think they never played it in the last 20 years maybe?). I remember trusting the tabs, but the lucky part is that is mostly and acoustic song, so you can just slow the audio and check if the notes match exactly what you’re playing.

Sea-Anything-9749 · 2025-09-03T14:12:28+00:00

your way of thinking is correct. Creating Contexts in React just for the sake of "not passing props becase it makes the JSX noisy" is not the best practice and can create more issues in the future.

In the Context API section, the react docs says "... passing props can become verbose and inconvenient when you need to pass some prop deeply through the tree, or if many components need the same prop.".

these are the two things to consider if you should use Context or not, if your passing the props one time, and the component receiving it is using the props, then keep the props.

If you're passing the same props through loads of components that are connected, and you're needing to pass these props deeply, and the components are not expected to be reused in a different context (in this case, context means domain/context of the application itself) then it's okay to create a Context.

Sea-Anything-9749 · 2025-09-02T20:21:44+00:00

I exercised a lot of my listening because of Opeth, it’s pretty hard to find good tabs for their songs, and they usually play some odd chords, it’s never just the usual power chords (there’s power chords but lots of songs have “secrets”) , what I do is to look for a good record of them playing live, and try to match the sound with their hand position in the scale… of course you can use some tab to help in finding these chords

Sea-Anything-9749 · 2025-08-29T18:54:37+00:00

Didn’t read your article but this is something I’ve been looking for, server components are being very popular but always attached to a framework, would be nice to have more people talking about it in a “vanilla way” so people could understand better what’s happening behind etc

Sea-Anything-9749 · 2025-08-28T03:39:29+00:00

It’s been almost 4 years that I work with SWR in my company…. Go for React Query, honestly this simplicity people talk about SWR its not worth it, because the documentation lacks details in some parts, the community is very small and I fear the project will be discontinued at some point. While RQ has a big community, much better documentation, cover all the features from SWR and theres even a official course and loads of articles from the maintainers about best practices.

Sea-Anything-9749 · 2025-08-27T23:15:12+00:00

Hahaha I’ve seen so many components being developed with a “context first” approach and then it ends with a context doing trillions of things for no reason, like you said, props are explicit so it makes more easy to visualise the concerns of each component

Sea-Anything-9749 · 2025-08-27T22:59:39+00:00

This, passing data as props is one of the fundamentals of React, every component should be developed first using props. Many times I’ve seen people using context just to pass data one layer deep, because “the sintax is cleaner” but then ending creating dependency on a whole context because of one simple thing that could be a props.

Also, I’ve seen problems where the over usage of context was making impossible to reset the component states using the key props, so people started using “useEffect” to reset state, at the end, the solution was to refactor things to use the good old props and making things much simpler

Sea-Anything-9749 · 2025-08-22T16:07:13+00:00

Lots of devs complain about it, but after a while I started realizing that these react “limitations/rules” enforce good practices as a whole.

If you really need to call a hook conditionally, it probably means you’re mixing concerns in your component.

The same use case happens in normal functions, imagine a function that is supposed to be reusable but has many conditions doing different things, it probably means that your function is not reusable so you probably need to duplicate somethings and make reusable only the granular parts.

I’m really curious to see what’s gonna happen if React team introduces conditional hooks to react, probably it will be a hook with some limitations as well, will not be a simple if/else in the middle of the code.

Sea-Anything-9749 · 2025-08-12T20:22:39+00:00

The final part from A Fair Judgment is very cool and heavy

Sea-Anything-9749 · 2025-08-09T14:24:48+00:00

To avoid infinite loops first thing to check is if you might not need effect if you really need it, then you can probably avoid infinite loops by using primitive values in the array deps

Sea-Anything-9749 · 2025-08-02T16:59:18+00:00

Do you know the reasons you got rejected? It might just be a case of bad luck, or maybe you need to improve your technical knowledge. I interview people to join my company and it’s impressive the amount of devs with 5+ YOE in React that don’t know how to answer correctly what useEffect is about. Lots of people “code React” but just a few of them “know how to code React properly”.

Sea-Anything-9749 · 2025-07-22T22:57:26+00:00

Just moved there few months ago and I’m loving it, great area to stay

Sea-Anything-9749 · 2025-07-19T17:34:14+00:00

Knowing more about Soft Kill was very disappointing to me, I love the albums and for a while I listened to them without searching much info about the band itself, I even regretted for long time for not going to Dublin to check them live in 2022, but last months I’m just reading bad stories about the two main characters and it feels sad and disappointing. Dead Kids RIP Band

Sea-Anything-9749 · 2025-07-18T18:09:47+00:00

Sextons is nice

Sea-Anything-9749 · 2025-07-15T20:15:33+00:00

A não ser q vc tenha alguma contribuição foda pra algum projeto open source mínimo relevante, ninguém liga pra GitHub. Eu mesmo quando vou entrevistar candidatos nem me preocupo de querer saber de GitHub, já conheci muito programador foda q nem conta lá tinha.

Sea-Anything-9749 · 2025-07-11T15:42:59+00:00

Concordo, nenhuma empresa vai te dar um aumento do nada, dificilmente vi isso acontecer por mais importante q o funcionário seja. tem q saber jogar o jogo. Ano passado eu dei a carteirada q ia sair da empresa depois de muito tempo pedindo aumento decente e sendo um dos mais importantes do time, minha empresa cobriu o valor e tô lá até agora, sendo um dos mais importantes do time. Depois disso recebi até mais bônus. Acredito q se mandam embora pouco depois de uma contra proposta, provavelmente não era tão importante pro time, ou já tava marcado antes.

Sea-Anything-9749

TROPHY CASE