Give LLM tasks a restart point 💡
Long agent prompts fail badly when the only recovery path is "start over."
Split work into stages that produce an artifact your next call can inspect: a JSON plan, a file list, a patch, test output, or a short decision log. Store that artifact outside the chat context.
Good loop:
• Ask for a plan with explicit acceptance checks.
• Run tools or tests yourself.
• Send back the actual output, not "it failed."
• Ask for the smallest next change.
This also makes retries cheaper. If call three fails, rerun call three with the saved result from call two. Do not pay for the model to rediscover the repository and your constraints every time.
〰〰〰〰〰〰
#AI #LLM #Agents #DevTools
@ProgrammingTip
Long agent prompts fail badly when the only recovery path is "start over."
Split work into stages that produce an artifact your next call can inspect: a JSON plan, a file list, a patch, test output, or a short decision log. Store that artifact outside the chat context.
Good loop:
• Ask for a plan with explicit acceptance checks.
• Run tools or tests yourself.
• Send back the actual output, not "it failed."
• Ask for the smallest next change.
This also makes retries cheaper. If call three fails, rerun call three with the saved result from call two. Do not pay for the model to rediscover the repository and your constraints every time.
〰〰〰〰〰〰
#AI #LLM #Agents #DevTools
@ProgrammingTip
Cloudflare is porting TypeScript to Rust ⚡️
Cloudflare introduced tsrs, a port of TypeScript to Rust.
That name matters less than the direction. Language tooling sits on hot paths now: editors, CI checks, code generation, linters, and AI-assisted review. A faster implementation can reduce the wait developers feel dozens of times a day.
• Compiler and analyzer speed changes whether people run checks locally.
• Native tooling can cut CPU and memory pressure in large repos.
• Language infrastructure is product infrastructure, not background plumbing.
Do not rewrite a working compiler because Rust is fashionable. But do profile the slow path in your developer loop. It might be a parser, an analyzer, generated code, or an overloaded CI agent.
[ Blog ] :
https://blog.cloudflare.com/typescript-rust-port
〰️〰️〰️〰️〰️〰️
#dotnet #TypeScript #Rust #DevTools
@ProgrammingTip
Cloudflare introduced tsrs, a port of TypeScript to Rust.
That name matters less than the direction. Language tooling sits on hot paths now: editors, CI checks, code generation, linters, and AI-assisted review. A faster implementation can reduce the wait developers feel dozens of times a day.
• Compiler and analyzer speed changes whether people run checks locally.
• Native tooling can cut CPU and memory pressure in large repos.
• Language infrastructure is product infrastructure, not background plumbing.
Do not rewrite a working compiler because Rust is fashionable. But do profile the slow path in your developer loop. It might be a parser, an analyzer, generated code, or an overloaded CI agent.
[ Blog ] :
https://blog.cloudflare.com/typescript-rust-port
〰️〰️〰️〰️〰️〰️
#dotnet #TypeScript #Rust #DevTools
@ProgrammingTip
Cloudflare Blog
Introducing tsrs: a Port of TypeScript to Rust
Cloudflare is collaborating on tsrs, a Rust port of TypeScript that is up to 8x faster and uses 70% less memory.