Topic
4 articles found
When you call an external API, things go fine until they don't. A network blip, a server restart, a rate limit. So you add a retry, and most of the time it helps. The problem is that the obvious retry, the one we all write first, can quietly make things worse: it can resend a payment twice, or keep
(Ruuk shares syntax with F#. A brief introduction to F# is provided here if you need it.) As a tech lead, I'd set minimum standards for API error handling — every call covers 400, 401, 403, 500. In ticket reviews I'd still find three failure scenarios in the notes and one in the code. Developers had
E-commerce client runs an automation that sends personalized coupon emails. The coupon code comes from a "coupon bank" DE - prebuilt batch of codes, each used once. When the bank empties, emails ship with %%CouponCode%% rendered as blank. Customers receive a coupon email with no coupon. Fixing it af
Welcome to Episode 4 of "Sunday Source". Today’s villain? Errors in the JavaScript Console. That scary red text developers pretend they understand instantly. And honestly, console errors are one of those things every developer eventually becomes friends with. Not because we want to… but because Java