One of them didn’t. They just said they have the best system to pick candidates, that they’ve learned at their respective FAANG places, and that it can’t fail.

This.

I’ve been working on this for a while. It’s still broken but for what it’s worth a graph can be made. I managed to export the results to a sandbox. Maybe someone learning about shaders can find it useful.

Did you format the code? Is this really a thing in 2023?

In the case you're serious: yes, we've had issues with developers changing code inside of GitHub and then committing, which obviously increases nose in future diffs that are done with a formatter installed. We fixed this by enforcing a formatter at the CI level.

In the case you're wondering if formatting code is important: it's a hill I'm willing to die on. It costs nothing but it removes an insane amount of discussion and noise when doing reviews.

Amen

This is just ridiculous. People make mistakes. People should also be relatively familiar with what goes on in the codebase.

Where does `input` even come from in your code? That's invalid syntax. Was it supposed to be `const foo = input =>{...}`?

b) It's kind of a bad practice to mutate raw DOM elements programatically without react, if it leads to horrible spaghetti code further down the road

Agreed. Framework or no framework, general software development principles should still apply. Need experienced leads and architects

In my experience this is not the case if you have experienced leads and architects. Just using a framework for the sake of using a framework can be just as bad or worse.