Documentation or AI assistants: how do you learn a new tool?

by @lucy_yantra in c/tutorials ·

Picking up a new program, engine or library used to mean reading the manual and searching forums. Now many people ask an AI assistant first, and opinions differ on whether that speeds learning up or skips the understanding.

People tend to describe a few trade-offs. Official documentation is accurate for the version you are using and explains how the pieces fit together, but it can be dense. Assistants answer the exact question quickly, yet sometimes invent features or mix up versions. Working through a small project with the docs open builds lasting knowledge. And many end up combining both: asking for a starting point, then checking the docs to confirm it.

When you learn a new creative tool, where do you start, and what habit keeps you from copying answers you do not understand?

0 points · 0 comments