[milani]

> I don't need to trade that for need to spend time to know what and more importantly why something is where it is.

I had two options: 1. Learn everything first and then start prototyping. 2. Start prototyping and learn along the way. I chose the latter. But instead of searching stackoverflow and putting the pieces together, I used GPT and learned from the generated outputs in the context of my own problem.

It may not save a lot of time in larger projects because as you said, one should ultimately learn the "what and why", but it definitely provides a more pleasing experience. And I guess the time-saving part becomes more relevant with better tooling, like the suggestion I had.

[Aperocky]

Fair - I guess I'm just used to the old ways and hated things showing up without me specifically telling them to show up there first. But then, I still learn while prototyping, ChatGPT might be easier since it does give you a template to go off of.

But then, I don't think this really go beyond entry level prototyping, any complexity and chatGPT doesn't have enough tokens.