Task setup, retries, queues, real-time observability, and the self-hosting gotchas the quickstart skips. Most background job solutions feel like infrastructure problems wearing an API costume. You spend more time configuring Redis queues and worker pools than actually building the tasks you need to run. Trigger.dev takes a different approach: background tasks are TypeScript functions that live in your codebase. You write them like normal code, deploy them with your app, and Trigger.dev handles the scheduling, retries, queuing, and observability. Here’s how to get your first task running and what to watch out for when you go to production.…