This archive page features articles where the blog authors publicly share their development processes, successes, and setbacks while building and deploying software solutions on the .NET and Azure platforms, with a focus on AI-powered applications. By doing so, they highlight the importance of iteration, experimentation, and transparency in software engineering, providing valuable insights into th…
11 articles since Aug 2026
A security review of MockEvalio found admin auth silently broken, a cross-tenant data leak, and a hardcoded key that traced straight back to the project's second commit, five months earlier.
I tested MockEvalio's new Stripe checkout end-to-end — real test card, real webhook signature. Three hours later, the buttons meant to get someone there were silently broken.
I built a complete system to measure whether MockEvalio's AI evaluator is accurate — comparison logic, deviation thresholds, a calibration worker, an admin dashboard. I never built the one piece that would let it run.
In thirty-three minutes, MockEvalio went from calling Groq directly from five different services to a centralized orchestrator with versioned prompts and cost-aware multi-provider routing. What built on what, and what's never been touched since.
MockEvalio's single ₹399 plan became three separate prices within nine hours of its first real payment. The change is fully on the record. The reasoning isn't, and I looked.
I built full OpenTelemetry coverage into MockEvalio over one night. By morning, part of what I'd just built was already too loud to keep as-is.