pailhead

4 ms·

1. 1.▲
   by pailhead 1y ago

   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.
2. 2.▲
   by pailhead 1y ago

   This.
3. 3.▲
   A node shader editor for Three.js [video](youtube.com)

   1 points by pailhead 2y ago|1 comments
4. 4.▲
   by pailhead 2y ago

   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.
5. 5.▲
   by pailhead 3y ago

   Did you format the code? Is this really a thing in 2023?
6. 6.▲
   by pailhead 3y ago

   Amen
7. 7.▲
   by pailhead 3y ago

   This is just ridiculous. People make mistakes. People should also be relatively familiar with what goes on in the codebase.
8. 8.▲
   by pailhead 7y ago

   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 h
9. 9.▲
   by pailhead 7y ago

   Agreed. Framework or no framework, general software development principles should still apply. Need experienced leads and architects
10. 10.▲
    by pailhead 7y ago

    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.
11. 11.▲
    High level overview of three.js(medium.com)

    1 points by pailhead 8y ago|0 comments