Under the hood it's still software — servers, versions, an interface. What's new is the front door: you don't learn its commands, you just talk to it.
It's still just software — servers, version numbers, an API humming underneath. I find that oddly reassuring: like any software, it rewards understanding how it works and where it breaks. What's genuinely new is only the front door — and that changes everything about how we approach it.
For the first time, the software can explain its own use. Stuck on how to approach something? Don't go hunting for documentation — ask the tool itself.
Here's how I'd think about it: start with what they already enjoy — a game, a sport, a show — and find books that echo it. Favor short chapters, a strong voice, and a fast opening. Offer two or three, never ten. And graphic novels absolutely count. Want me to turn that into a reference-interview checklist you can reuse at the desk?