Learning note / Independent learning
Prompt Engineering
I treat prompting as part of learning to work with AI tools deliberately. It connects to how I explain requirements: the tool needs a task, relevant context, and a result I can judge.
Writing down the actual request
A vague instruction leaves the model to guess what matters. I find it more useful to identify the audience, the information available, and the constraints before asking for an answer.
Examples help when a format or distinction is difficult to describe. They are a way to communicate expectations, rather than a guarantee that the result will be correct.
Keeping an output reviewable
For a larger task, I want intermediate results that I can inspect. A proposed structure, a small change, or an explanation of assumptions is easier to judge than a long answer that hides several decisions.
That keeps the work connected to the original requirement as it develops.
The judgment I still need to supply
I do not treat a confident response as evidence. With generated code or factual claims, I still need to check the relevant sources and behavior. This is especially relevant to the AI-assisted implementation documented in my Nutras website work.
What I take forward
- State the task, context, and constraints.
- Ask for results that can be inspected.
- Verify generated claims and behavior.