The better you are at architecting or even directing a junior developer, the better your output too. Dont let AI make decisions, its supposed to take your decisions and turn those into code. When AI makes decisions, well the unexpected outcome is always on you.

A weekend is enough to get going, but not nearly enough to 'be on par' with everyone else.

That said - what we have learned in the last year could be compressed quite a lot - there are a lot steps we could skip, and 'learn by failure' that need not be repeated.

It takes a while to get the subtleties of it, it's among the most highly nuanced things we've ever encountered.

Just learn, sure. But the difference between my efficiency of using it on my day 2 and month 6 is significant. Yet I feel I am barely scratching the surface of it.

Firmly disagree. Learning how to use these tools effectively is unintuitively difficult.

They're great at some stuff and terrible at other stuff in ways that are very hard to predict.

I'm figuring out new and better ways to use them in a daily basis, and I've been an almost daily user for nearly three years.

> a weekend would be enough to be on par with everyone else in the industry

I kind of agree in general that it is a learned skill, but considering how unclear people generally are when they communicate, I'm guessing it'll take longer than a weekend to be able to catch up, especially catch up to people who've been working on precise and careful communication and language for years already in a professional environment.

/thread

If one has been reading a wide variety of books/papers/articles/whatever their whole life, and one has been mindful of how to communicate with the "written word" as it were, it takes about 3 hours to be wildly effective with this technology. I think it took longer to learn google-fu than it did to learn how to use this technology effectively.