Tiered Verification: When 'Failed' Is the Wrong Answer
The all-or-nothing verifier was failing jobs that produced visually perfect output. Here's how three verdicts replaced a binary gate.
Read post →Engineering
A chronological record of every major architectural decision, bug, and tradeoff behind the pipeline — from the first commit to production.
The all-or-nothing verifier was failing jobs that produced visually perfect output. Here's how three verdicts replaced a binary gate.
Read post →Machine epsilon caused a Lanczos scale step which caused a pixel provenance failure. A three-layer causation chain, one line fix.
Read post →“Reframe this video” means something different for a podcast versus an action sequence. Here's how 9 presets and a custom weight builder solved it.
Read post →Early users uploaded portrait and square videos. The pipeline rejected them. Here’s how SourceMetadata was refactored to support multiple output ratios.
Read post →Zero SSR, fully static, served from S3. The constraints are real but the tradeoffs were worth it. Six API contract mismatches discovered at UAT.
Read post →The complete SaaS API surface: job lifecycle, tier gating, auth, billing, webhooks. And two packaging landmines you won’t find in any docs.
Read post →VPC, RDS, SQS, AWS Batch, three Lambda workers, CloudFront, S3 — all in Pulumi Python. And the reserved env var that costs you a failed deploy.
Read post →Before any cloud infrastructure, before any API — there was a Python pipeline with one rule: every output pixel must be a direct copy of a source pixel.
Read post →