A developer must follow a checklist before writing any script. This ensures the script runs correctly, efficiently, and safely. The checklist helps prevent common errors and unexpected costs.
By Pawan Nayar · from the LLOS AI Learning record
A developer must follow a checklist before writing any script.
This ensures the script runs correctly, efficiently, and safely. The checklist helps prevent common errors and unexpected costs.
Before writing a script, a developer must check several items. These checks depend on the type of script. The checks cover asynchronous operations, API calls, file handling, and time estimates. They also cover long-running commands, session settings, and UI changes. Following these steps helps avoid problems.
A developer plans to write a script that calls an API many times. The developer checks the 'Batch API Job' section of the checklist. The developer confirms the correct model is chosen and tests the script with a small number of calls. This prevents using an expensive model for a simple task or running a broken script for a long time.
Resolved from this lesson's own record — real definitions, not invented for this page.
More from the same record, pulled by shared topic — not written new for this page.
Before editing, the developer must confirm the exact start and end points for the changes. The developer must only change text within these points.
When a developer creates or changes a file, the developer must state its full path. The developer must list all full file paths at the end of the conversation.
A developer must always ask for permission before spending money on an AI model. This includes small test runs.
An AI model must state the full path every time it creates or changes a file. The AI model must list all full paths at the end of a conversation.
A developer must follow a checklist before writing any script. This ensures the script runs correctly, efficiently, and safely. The checklist helps prevent common errors and unexpected costs.