Comment by Blaine Garrett on "How will GPT-3 change the Frontend developer eco-system"

This is really interesting and the first I have heard of it. Thank you for sharing.

In a general sense, this simply feel like a smarter scafolding tool and part of the Low Code movement. My impression of Low Code is that you're stuck with brittle unmanageable systems, which might be fine for initial rapid prototyping but tend to require devs to actually build the thing from scratch for real world usage.

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.

Utkarsh Bhimte great insight. In the "teaching a child" analogy, from what you gather does each instance need to be independently "taught" or is there the idea of some sort of database of knowledge? I could see it go both ways. It would be cumbersome to teach from scratch but also susceptible to bias or opinion if there is a global data base. eg. the "Ugly emoji" example from the video. What is "ugly"?

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.

Search Hashnode