@nexoupdates

Practical notes

AI, without
the noise.

How the tools work, when to use them, and how to keep the last pass.

Start

Name the outcome before you name the model.

Nexo Updates at a quiet desk: a white helmet with a blue light, a microphone, a laptop, and a mug.

The desk

Where the last pass happens.

The notes on this page are written here, then read again before they are published.

What AI is actually doing

It does not know your job. It predicts the next useful piece of text, image, or code from the material you give it.

  • Language

    Chat models guess the next word, then the next. That is why they can write a clean email and still invent a date. Give them the facts in the prompt if those facts have to survive.

  • Images

    Image tools paint from a description: subject, light, lens, and what must not appear. The first picture is a sketch. Change one instruction and generate again.

  • Code

    Coding tools read the files you open. Point at the error, the test, and the behavior you want. You still run it. A confident patch can still be wrong.

  • Search

    Research tools look things up and summarize. Ask for the links with the answer. Open the pages. Keep a claim only if you can find it there.

Notes we keep repeating

Three ideas that still apply, whatever the product is called this month.

  • How to use it

    Brief it like a colleague

    Skip “help me write.” Say who will read it, how long it should be, the tone, and the one sentence that cannot change. If you have an example of the result you want, paste that too.

  • Accuracy

    Stay near the source

    Models complete a pattern. They do not look up your invoice unless you paste it or use a tool that shows pages. Smooth writing is not evidence. Numbers, names, and quotes need a source you can open.

  • Judgment

    Keep the last pass

    Let the tool face the blank page. Keep the final read for yourself: names, numbers, tone, secrets, and anything a stranger would take as a promise. If it spends money or sends a message, a person stays in the loop.

A prompt that actually works

Five parts. Use the ones you need. Empty prompts produce average work.

  1. 01

    Role

    Who it is for this task. A careful editor. A senior engineer. A photographer.

  2. 02

    Job

    The finished thing in one line. Not “help with this.” The email, the patch, the crop.

  3. 03

    Material

    The draft, notes, error, brand words, or a photo of the product. Context beats adjectives.

  4. 04

    Limits

    Length, reading level, what to avoid, what must stay. One constraint is better than ten vibes.

  5. 05

    Shape

    Bullets. A table. Code only. A subject line and a body. Tell it how the answer should look.

A way to use any of them

The names change. The sequence does not.

  1. 01

    Name the job

    Write the finished thing in one line. An email a client can forward. A patch that fixes the failing test. A picture of the product on a wooden table, morning light, no text.

  2. 02

    Bring the material

    Empty prompts produce average work. Paste the draft, the notes, the error, the brand words, or an example of the result you actually want.

  3. 03

    Change one thing

    Ask for shorter. Then warmer. Then the missing example. One change at a time, so you can tell what helped.

  4. 04

    Leave with a check

    Before it is sent, published, or merged, confirm the facts, cut the filler, and make sure it sounds like you.

Choose by the job

Pick the tool that fits the work, then give it something real to work on.

  • Write

    Drafts, rewrites, and cuts. Tell it the reader and the length, then ask for a tighter second version. For facts, paste the source or it will fill the gaps.

    ChatGPT, Claude, Gemini

  • Picture

    Describe the subject, the light, the crop, and what must not appear. Treat the first result as a sketch. Repeat with one change.

    Midjourney and the image tools in the chat apps

  • Code

    Open the tool in the project. Point it at the file, the error, and the behavior you want. Run the tests yourself. Keep diffs small enough to read.

    Cursor, Copilot, and other coding agents

  • Research

    Ask for the sources with the summary. Open the pages. Keep a claim only if you can find it there. A citation you cannot click is not a source.

    Perplexity, NotebookLM

  • Transcribe

    Record the meeting, then ask for decisions, owners, and open questions. Correct the names before you send it. Do not paste a private call into a public tool.

    Whisper and built-in recorders

  • Automate

    Start with one repeated task you can describe in a sentence. Keep a person on any step that spends money or sends a message. Save the prompt next to the file it works on.

    A saved prompt on a file, form, or calendar

Watch for this

  • It can sound sure and still be wrong

    If a number, quote, or law would matter in court or in a client email, find it outside the chat.

  • It will use whatever you paste

    Do not put passwords, private customer files, or unreleased work into a tool you do not control.

  • It copies the average

    Without your notes and your examples, you get the internet’s middle. That is rarely the voice you want.

The tools will change.
This will not.

Name the job. Bring the real material. Check the result before it leaves your hands.

Instagram @nexoupdates

nexoupdates.online