Dako's AI Builder Notes
⌘K
中EN
System
Color theme
Changsha HubOffline
大可 Dako
大可 Dako大可 DakoAI Builder · Agent PractitionerTurning AI into working software. Practical notes on agent engineering, vibe coding, and commercial delivery.
Platform links coming soon
The first job trains the method. It is not a bet.GoodClear rules, reversible, obviously right orwrongOne closed loop leaves a methodNext time, swap the sourceBadWide scope, irreversible, needs a meeting tojudgeYou babysit, and you cannot accept the resultPatience dies firstWin one small job you can turn in
The first job trains the handoff. It does not prove the product can do everything.

Pick the First Job Carefully

Do not spend the first run on a high-stakes end-to-end job. Pick work that is low-risk, reversible, and obviously right or wrong.

Plenty of people spend the first run asking the product to finish a whole job end to end. Scope blows up, every step needs a nod, and nobody can tell if the result is right without a meeting. Patience dies before the method exists. The first job has one purpose: run stop asking, assign the work as a closed loop.

After reading, you should be able to answer:

  • What three tests does a good first job pass?
  • Which jobs look impressive and still should not be first?
  • After one success, what is worth keeping?

All three tests, or it is not first

  1. Speakable rules: you can write the object, result, and format in a few sentences. No hidden house rules.
  2. Reversible action: a bad output can be thrown away; the original is intact. Pay, send, overwrite, merge to main — none of that is a first job.
  3. Obviously right or wrong: open the file and check, or run one command and get green or red. If it takes a meeting, it is not first.

On the coding side, the official start is still “pick a folder, state a goal,” not “hand over the system.”codex-quickstart Cloud teammates are the same: one closed real job before a fleet.xai-bot

Impressive, but not first

  • Rewrite a whole module, or draft a full external proposal, in one go.
  • Work that cannot start until every company doc and inbox is connected.
  • No acceptance line, only “make it look right.”
  • An irreversible act buried in the middle, with no stop.

Those jobs are not forever off limits. You do not have a method yet. Add complexity before the method exists, and the failure gets blamed on the product. Next time you will assign even less.

Keep the method, not a lucky run

A finished first loop should leave three things: the five-part brief, the stops you actually used, and a result you checked. Next time you swap the source material, not the skeleton. That is what “keep” means later. How the five steps run is in the five-step loop.

References

  1. Codex / ChatGPT quickstart
  2. Grok Bot — xAI