Been using this one for quite a while now. Sometimes you need to share AI conversations for context. My rule of thumb is that I human summarize and contextualize like I would normally, then in a thread below it, fork off an ai;dr quoted reply. Makes it like optional reading.

The handiman who works for my family quite often is not super technical. He was troubleshooting a mini split for me and I walked out to see him vocally chatting with chat gpt going through error codes, handless.

He found a use, and you'd be wrong to assume "trades" are safe from the chatbot. That doesn't mean his job is going away, but maybe he can do more solo jobs and doesn't need a helper all the time. Or maybe he does his jobs faster. Who knows!

People don't need to know model names to find a use.

Pagination of data out of a database is why you do it. Or rather, why I've done it in the past. Expanding on this, for the reporting of data so you can join that static data with non static data.

Legally it isn't, actually. Morally, yes.

Check out "AI has a labor issue, not a copyright issue" chapter of "The Reverse Centaur's Guide to Life After AI" by Cory Doctorow

It's a hard chapter to read, but it's important to understand.

EDIT: I love the downvotes for speaking the truth, seriously people, please understand. It's important.

An AI rewrite is just open source with more steps

I've run this experiment on myself a great number of times.

Your story is correct, sometimes. It's not correct all of the time. Sometimes AI is slower and the output is better (think: pair programming). Sometimes AI gets me the first draft and the cognitive understanding takes time (overall, for me, usually faster, but sometimes slower I will readily admit). I'm really good at reading code, I guess? And still other times it will one shot near perfection (in true slot machine fashion). It'll also produce absolute shit, as well, frequently.

My firm point to you is it's not a blanket truth.

Listen, I'm a VERY healthy skeptic of AI on a number of fronts, but saying it can't speed things up is just not true.

I feel like I understand where you're trying to come from with the argument about skill degradation, but the flat statement you say here is undeniably false.

So, parliament + prime minister?

Why blur the shirt text? Show it for what it is!

I finally found it, it's like 300 pages of individual rejections you need to go. Hard pass.

Not listing the specific game release, more the game epoch:

• Civilization
• World of Warcraft
• StarCraft
• Sim City
• Quake

You world be very surprised. It's not what I directly work on, but there are entire programs dedicated to tracking and lowering the cost of password and account resets (and doing it securely). That last part is the hard thing. Large organizations can save millions of dollars if they can get people to not lose/forget their credentials -or- self service those resets (but even then, having that person do it is now losing their time and energy).

It's not just indirect opportunity costs either, it's direct costs to the IT organization. Smaller teams can absorb this stuff as a rounding error on their time, but the second you're counting in the thousands, you need to deal with this type of thing. (And I'll repeat: securely)

Now imagine doing it as a B2C+B2B organization like Google or Microsoft. The costs are staggering.