This is making assumptions about the work I do which don't happen to be valid.
For example:
> libraries that [...] have star counts in the high thousands at least
Play little to no role in my work, and
> I'll let it convert css/style objects/etc into tailwind
Is something I simply don't have a use for.
Clearly your mileage varies, and that's fine. What I've found is that for the sort of task I farm out to the chatbots, the time spent explaining myself clearly, showing it counterexamples when it gets things wrong, and otherwise verifying that the code is fit to purpose, is right around the time I would spend on the task to begin with.
But it's less effort, which is good. I find that at least as valuable if not more so.
> producing documentation
Yikes. Not looking forward to that in the future.
I remember watching this really funny video where a writer, by trade, was talking about recent AI products they were exploring.
They saw a "Make longer" button which took some text and made it longer by fluffing it out. He was saying that it was the antithesis of his entire career.
As a high schooler who really didn't care, I would've loved it, though.
He said they don't want to have situation when sender is using chatgpt to write a fancy mail and recipient is using chatgpt to read it. However I think that it is the direction where we are going right now.
Not sure why you are scared of GPT assisted documentation. First drafts are universally garbage, honestly I expect GPT to produce a better and more accurate first draft in a fraction of the time, which should encourage a lot of people who otherwise wouldn't have documented at all to produce passable documentation.
> Yikes. Not looking forward to that in the future.
Instead of documentation, I'm hoping more for "analysis". A helper that can take in a whole project (legacy or not) and tell you what it's supposed to be doing, and maybe point out areas for improvement.