PostgreSQL Query Rewriting Techniques The previous articles in this series covered performance problems you fix by adding indexes, restructuring joins, or tuning memory. This one is about the queries where the plan is "fine" — every node is doing something reasonable — but the query itself is asking the wrong question, producing unnecessarily large intermediate results or forcing the planner dow
SMS remains one of the most reliable communication channels available today, with open rates exceeding 90%. Whether you are building an OTP SMS API for authentication, setting up transactional alerts, or automating marketing workflows, a robust SMS API integration is a powerful addition to any stack. In this tutorial, we will explore how a REST SMS API works and walk through a practical implementa
I watched 30 users talk to the same voice agent Same script. Same questions. The only thing I changed was the response latency: 300ms, 500ms, 800ms. At 300ms, people just talked. No awkward pauses, no confusion. One user didn't even realize it was an AI until I told her afterward. At 500ms, something shifted. Users started talking over the agent. They'd ask a question, wait half a second, then r
Most async APIs commit to one thing: starting your job. They return 202 Accepted, hand you a job ID, and that's where the contract ends. The rest is your problem. I do something different. I make one promise: When your job is done, I'll tell you accurately. Until then, I'll keep retrying. That's the entire contract for everything I've ever shipped. It sounds small. In practice, it's the only thing
We have reached a small but important milestone for DondeGo API. The first working use case is already live: we are using our API to power daily event selections for two local projects: https://x.com/HoyBcn https://x.com/EnMadridHoy The idea is simple: every day, the system uses DondeGo data to select some of the best events happening today in Barcelona and Madrid. Instead of manually searching ac
How intentional loading decisions keep your app fast at scale. Frontend performance is not a late-stage cleanup task. It’s not tech debt. It’s a set of decisions we make every day while we code — what we load, when we load it, and how we render it. The answer depends on the importance of the code, its size, and when the user actually needs it. Get that wrong, and the browser pays for everything
Originally published at ffmpeg-micro.com You need a thumbnail from a video file. Maybe you're building a video gallery, generating preview images for a CMS, or creating social media cards from uploaded content. The usual advice is to install FFmpeg on your server and write extraction scripts. That works until you need it in production. FFmpeg can extract a single frame from any video using two fla
Is your website throwing 502 errors whenever an external API starts lagging? It is a common engineering grind where slow dependencies choke your server and kill your response times. The fix is not adding more resources. It is about changing how you handle work. Stop making users wait for external processes to finish. Offload heavy tasks to background jobs and queues. Distinguish between workers