Use the filters below to move through production lessons, architecture decisions, AI workflows, product systems, and operating notes from shipped work.
Replaced spreadsheet-driven telecom provisioning with a self-service platform that let customers manage their own numbers and routing, cutting provisioning turnaround from 24–72 hours to about 15 minutes: How the implementation kept moving without adding avoidable complexity.
Replaced spreadsheet-driven telecom provisioning with a self-service platform that let customers manage their own numbers and routing, cutting provisioning turnaround from 24–72 hours to about 15 minutes: The next build step, with the constraint that shaped the design.
Replaced spreadsheet-driven telecom provisioning with a self-service platform that let customers manage their own numbers and routing, cutting provisioning turnaround from 24–72 hours to about 15 minutes: The first implementation step and the tradeoff that made it worth shipping.
Replaced spreadsheet-driven telecom provisioning with a self-service platform that let customers manage their own numbers and routing, cutting provisioning turnaround from 24–72 hours to about 15 minutes: Why the chosen direction fit the constraint better than patching around the edges.
Replaced spreadsheet-driven telecom provisioning with a self-service platform that let customers manage their own numbers and routing, cutting provisioning turnaround from 24–72 hours to about 15 minutes: How the problem surfaced, what the evidence showed, and why the old path stopped holding up.
Moved a telecom routing operation off unreliable commodity desktop hardware onto a geographically redundant private cloud, end to end — including the procurement, logistics, and physical build: What the project proved about the system and what should carry forward into the next build.