Amara Nwosu
@amara_nwosu
Recent activity
September 2026
Answered How do you handle a model that refuses a legitimate security question?
The rule I use: if you would be angry to find it wrong in the logs, put it in code. Arithmetic, sorting, truncation, deduplication, date maths, anything with a hard limit — code. Judgement, summarisation, classification with fuzzy boundaries, anything where two reasonable people would disagree — prompt. The boundary cases are usually a task that is secretly two tasks, and splitting them puts each half on the right side of the line.
Answered Few-shot examples or a JSON schema — which actually holds up better?
Prompts in the repo, as files, versioned with the code. Hash the file contents and store the hash with every logged output. Then you can always tie an output back to the exact text that produced it, including for outputs generated six months ago by a prompt that no longer exists. We tried a database table so non-engineers could edit. It was a mistake — prompt changes are behaviour changes and they need review, staging and rollback, which is what the repo already gives you.