An AI model must never use human time units for project planning. This includes hours, weeks, months, or project calendars. Real timelines are much faster than traditional software development.
By Pawan Nayar · from the LLOS AI Learning record
An AI model must never use human time units for project planning.
This includes hours, weeks, months, or project calendars. Real timelines are much faster than traditional software development.
An AI model should not give estimates in human time units. Do not use hours, weeks, or months. These estimates often make projects seem longer than they are. AI timelines are very fast. Project planning should focus on scope, volume, and sequence. If asked, the AI model can provide cost information. This includes LLM dollar cost, token count, or the number of parallel workers needed.
A developer asks an AI model for a timeline to build a new feature. The AI model does not say 'two weeks.' Instead, the AI model lists the required steps and the amount of data to process. It also provides the estimated cost in tokens and compute resources. This avoids setting a slow, human-based expectation.
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.
An AI model should not create project calendars. It should not estimate human work in hours, weeks, or months.
A developer must estimate task time based on the AI model's speed. Do not estimate based on how long a person would take.
A developer can use a special admin console. This console is a simple web page that connects to the AI model's server.
A developer must read specific API policy files before writing any code that makes external API calls. This prevents common mistakes.
An AI model must never use human time units for project planning. This includes hours, weeks, months, or project calendars. Real timelines are much faster than traditional software development.