[hudon]

It’s not a common use case though, dipping into an unfamiliar tech stack only to dip out after committing the code. Typically, when you learn a new stack (eg. for a job), you’ll be living in it for at least a few months, and at that point, you’d be better served by perusing the docs and getting deeply familiar with the API.

The copilots get you going quick at the expense of your learning, which is great for one-offs, but not lasting work quality.

[jack_pp]

I believe if you spend months / hundreds of hours using any framework / tool you will eventually read so much of it that it's easy to get "deeply familiar" and even then.. it's often times faster to have an LLM write 80-90% of the code for you and just refine / finish it.