HARRISON NDEKE / AI AUTOMATION BLOG

Field
Notes.

Practical articles on AI automation, agents, RAG, integrations, and the engineering work that keeps real systems dependable after launch.

Evidence firstHuman reviewedBuilt for implementation
Wordless dark basalt systems illustration with amber items moving through a central gate toward an ice-cyan completed grid, vermilion retry items in a narrow lane, an amber item in a clear reconciliation capsule, and a barrier blocking a full batch replay.FEATURED ARTICLE / 001

API design / batch processing / idempotency / workflow reliability

For a partial-success batch API, create a durable ledger before the call, classify every item from the response, and retry only items the provider explicitly left unprocessed or identifies as transiently failed. Treat a timeout or missing response as unknown, not failed: reconcile by an idempotency key or a read-back query before sending anything again.

Read the article

THE BLOG ARCHIVE

Systems worth
writing down.

Each article begins with a real implementation problem, distinguishes confirmed practice from judgment, and explains the trade-offs a production team should consider.

EDITORIAL STANDARD

Useful beats
loud.

This blog supports search and answer-engine visibility by publishing crawlable, source-backed explanations tied to Harrison’s real services and project evidence—not keyword stuffing, fabricated results, or generic AI summaries.

Discuss a system