Urgent.News

What's breaking now, across thousands of outlets.

More in Tech

Building FoxyInvoice — Chapter 7: CI/CD — push to main and it's live

This series is written in the open, from a real production system. This chapter is the deploy pipeline end to end, plus three real incidents where it quietly lied to us.

  • CI/CD pipeline runs gates in parallel for FoxyInvoice deployment
  • Health gates, SPA rebuild, and smoke tests follow API container checks
  • Three incidents reveal pipeline flaws: build failures, queueing issues, and YAML label mismatches

My fact-checker said CONFIRMED about a group that doesn't exist

I built a tool that fact-checks crypto claims. You paste a sentence like "Whales are holding $XYZ" and it plans the on-chain calls that claim needs, runs them against Nansen 's API, and answers…

  • Tool confidently confirmed non-existent wallets
  • Response declared claim as true despite non-existence
  • Highlights fundamental flaw in tool's design

When agents sped up, two teams hit the same wall: validation couldn't keep up

Agents made it faster to write code. Two engineering teams published what happened on the validation side when they did, and the two write-ups land on the same structural claim from opposite ends. Linear found its CI gate became the bottleneck. Salesforce found its human review stopped engaging.

  • Two engineering teams faced validation bottlenecks when speeding up AI-generated code.
  • Linear optimized validation by using faster third-party runners and AST-based linting.
  • Salesforce rebuilt review system to reconstruct intent and progressively disclose risk.

More from Wednesday 23 September →