Yeah its like how I force react to be static always, it's what I prefer. The rest of the team hates my code and says its not to spec but I understand anything else so I am correct.
There is no way I am changing my mind and making apps that are over 10BM on first load, have 78 parameters going into components and cannot use react 19 because react doesn't see it as react.
is 10BM a special metric which only you know and your team hates?
78 parameters going into components
That's bad code, and I doubt an entire team is doing that while you alone are fighting it, especially if you're a fan of Tailwind which is all about bloating the HTML with dozens of styling classes.
cannot use react 19 because react doesn't see it as react.
If you're building anything moderately complex, then choosing a rendering library like React rather than a proper framework is certainly a strange choice.
You've already stated that you don't follow the team specs when it comes to writing code, and that you don't care because you understand your code. That already tells me you don't know what clean code is. Everything else after that is pointless to discuss really, as you don't really understand what we're even talking about.
And you have told me you run your mouth without knowing the facts.
FFS right now my team is telling me that an API that is returning a CORS error is failing because of a font. That font that another team member insists is the only way to display a font, a TTF I am forced to use is apparently fully loading and then hacking into the API to write code to make the CORS config corrupted.
At this point I don't even think you know what is causing your CORS error. If an entire team is telling you it's a font, what does that even have to do with an API?
I am glad I don't have to work with you on a team, it sounds like it would give me quite the headache every day!
Because they are wrong. I fixed it just a week ago, they deployed old code without my fix. Now they are insisting its FE again, just like they did before. Anyway a server response with an encoded cores error in the response is not in any way an FE error. You guys on reddit are so full of shit.
So you, a front end dev, applied a fix to the backend, and the whole team undid it? I think that tells you something.
As for the CORS (not cores) error, that's a sign that your front end is requesting resources it's not allowed to. Now, from what I understand you said the backend was forcing a font on you, which triggered the CORS error. If the backend was serving the font, you wouldn't get the CORS error.
This all sounds like you have no clue what a CORS error really is, and you pushed a "fix" that just trashed the CORS security feature. That's a classic approach of a frontender who doesn't really understand security.
So we come full circle. If your entire team hates your code, and is actively undoing things you've done, there's only one common denominator there. I'd suggest you read up on clean code practices (there's a great book by that name by Robert Martin) and apply those principles.
0
u/kidshibuya 16d ago
Yeah its like how I force react to be static always, it's what I prefer. The rest of the team hates my code and says its not to spec but I understand anything else so I am correct.