The mindset shift
If you came from typing every character yourself, the hardest part isn't learning the tools. It's letting go of the keyboard.
Your old bottleneck was production — how fast you could write correct code. Your new bottleneck is specification and review — how clearly you can describe what you want and how well you can judge what comes back.
This changes what you optimize for:
- Before: memorize APIs (Application Programming Interfaces — the menus of commands a tool exposes), fight syntax, type fast.
- Now: describe intent precisely, decompose problems, evaluate output critically.
The engineers who thrive at this aren't the fastest typists. They're the ones with strong opinions about what "good" looks like and the discipline to reject output that doesn't meet the bar.
There's a second, quieter shift that catches people off guard: your relationship with not knowing. The old instinct was to stop and learn the before touching it. Now you can often generate a first pass in an unfamiliar stack and learn by reading it back. That's a real superpower — and a trap. Reading code you couldn't have written is fine. Shipping code you can't evaluate is not. The line is whether you can tell, with confidence, that the output is correct. Lean on the model to write faster than you can; never lean on it to know more than you're willing to verify.