@thasha
Nothing here yet.
Nothing here yet.
Apr 13 · 3 min read · Our API had 14 endpoints and 14 different error response formats. The mobile team spent 3 days writing separate error parsers for each one. I standardized everything to RFC 7807 with one DataWeave transform. TL;DR RFC 7807 defines a standard error f...
Join discussion
Apr 12 · 3 min read · Our bulk import API returned 200 OK on every request. Nobody noticed that 40% of records were failing silently for 3 days. TL;DR partition() from dw::core::Arrays splits an array into success/failure groups in one pass Build summary (total, succeede...
Join discussion
Apr 5 · 5 min read · I connected MuleSoft to GPT-4o last quarter for a support ticket classifier. The prompt builder worked (I covered that in a previous post). The LLM call worked. Then the response came back and my parser crashed. The LLM was supposed to return clean J...
Join discussion
Apr 5 · 3 min read · I connected a MuleSoft API to an LLM last quarter for a support ticket classifier. The API call was easy — the MuleSoft AI Connector handles that. Building the prompt payload from enterprise data? That's where I spent 2 hours debugging escape sequenc...
Join discussion
Apr 5 · 3 min read · I built a schema discovery function for a 6-system integration last year. Each source sent different types for the same fields. One function auto-detects types at runtime and builds a complete schema. TL;DR describeType function uses is operator cha...
Join discussion