The current developer eco-system agrees on the fact that algorithm whiteboarding is not the best approach to evaluate a dev for a frontend job. What could alternate strategies can the companies integrate for hiring developers?
Nothing here yet.
Nothing here yet.
The current developer eco-system agrees on the fact that algorithm whiteboarding is not the best approach to evaluate a dev for a frontend job. What could alternate strategies can the companies integrate for hiring developers?
Blaine Garrett I cannot confirm it as I have not experienced it first hand but I think the context can be inputted as initial config and then you can save them as presets. The bias on GPT-3 is also something that has been debated on twitter for some time now, there have been some disturbing statements. That is the exact reason why it is in such a close beta right now.
I can not agree more. I think this would bring up a new league of no-code tools where you can pick up the code and tweak it anytime. The level of customization of those would be nothing to be heard of. Also, the tool to be adapting those customizations and work on future development accordingly. I read somewhere that, priming a GPT-3 model is like teaching a child. A child who has the internet in its memory. That is the best analogy according to me. There are so many applications that I want to try out of this.