# Learning Without a Crutch — AI Coding Assistants: Use Them Well and Review Them Hard

Source: https://www.geekswithgeeks.com/en/ai-coding-assistants/learn-without-crutch

> Use an assistant as a tutor and reviewer while still building your own problem-solving skills.

## Struggle first, then ask

Skills grow when you **struggle productively**. If you ask for the full solution every time, you practise reading answers, not solving problems, and exams and interviews will expose the gap. A better routine: attempt the problem yourself first, then ask for a **hint** or a **review** of your solution, then ask the assistant to explain a better approach and **re-implement it from memory**. Ask "why does this work?" until you can explain it in your own words.

## Grow your skill, not just your output

Used well, an assistant speeds up learning. Used as a crutch, it weakens the skills you need most.

![Three habits: attempt first, understand always, share conventions.](assets/figures/ai-coding-assistants/section-7-map.svg) — Figure 7.1 — Attempt, understand and share.

## Prompts that teach

These ask for guidance rather than a finished answer.

```text
"Give me a hint for this problem, but do not show the solution."
"Here is my solution. Review it and point out bugs without rewriting it."
"Explain why this approach is O(n log n) and ask me a question to check I understood."
"Give me three similar practice problems, easy to hard."
```

## Gym with a spotter

A spotter helps when the weight is too heavy and keeps you safe, but if the spotter lifts the bar every time, your muscles never grow. Use the assistant to spot, not to lift.

**Quiz:** Which habit best builds your own skill?

- [ ] Asking for the full solution immediately
- [ ] Avoiding all practice
- [ ] Copying answers without reading
- [x] Attempting first, then asking for a hint or review

*Answer:* Attempting first, then asking for a hint or review. Effort followed by feedback is how problem-solving ability develops.
