Browsed by
Category: Spec Driven Development

Spec driven development flips the usual workflow: you write the specification first and let AI coding agents plan and implement it. These posts cover GitHub SpecKit, Copilot and real projects.

Document Extraction with GitHub SpecKit and Content Understanding Analyzers
Document Extraction with GitHub SpecKit and Content Understanding Analyzers

Document Extraction with GitHub SpecKit and Content Understanding Analyzers

Comments 0 Comment

My expense documents are usually airline receipts, hotel folios, parking tickets, a handwritten taxi slip. Some are PDFs, some are phone photos, and they come in German, English, Danish, Polish, or wherever I received them. Now imagine one backend that reads all of them and returns the same clean expense record every time. That is exactly what Content Understanding analyzers in Microsoft Foundry can do. And this time, I did not code them from scratch. Look at the picture. Documents…

Read More Read More

GitHub Actions OIDC for Azure: No More Expired Secrets
GitHub Actions OIDC for Azure: No More Expired Secrets

GitHub Actions OIDC for Azure: No More Expired Secrets

Happy Halloween! 🎃 Let me tell you a horror story. Recently, my pipeline stopped deploying. No code change, no failing test, just a red run. I wondered why, until it clicked: the client secret of my old service principal had expired. A zombie secret, haunting my pipeline. Annoying? Yes. Avoidable? Absolutely. The better way is GitHub Actions OIDC for Azure. It removes the secret completely. First, GitHub proves who your workflow is with a short-lived token. Next, Microsoft Entra ID checks…

Read More Read More

Spec-Driven Azure Infrastructure Before You Start Coding
Spec-Driven Azure Infrastructure Before You Start Coding

Spec-Driven Azure Infrastructure Before You Start Coding

What if you could describe your Azure environment in plain words and get it deployed – secure, cost-controlled, and repeatable? That is spec-driven Azure infrastructure. And you don’t need to be a cloud architect to try it. I restarted my Expenses Manager in June with one ambition: rebuild it without click ops. No portal wizards, no manual setup. That is why I use spec-driven development and rely on GitHub Copilot to assist me. In one of my previous posts, I…

Read More Read More

Never Pay for the Same Dataverse Mistake Twice
Never Pay for the Same Dataverse Mistake Twice

Never Pay for the Same Dataverse Mistake Twice

GitHub Copilot showed me something new: GPT-5.6 Sol, plus a 30% discount. Yes, and I couldn’t resist trying it on a Dataverse task. Why not see the new model in action, right? As a result, that decision burned nearly a month’s budget before the task was even done. But here’s the thing: the expensive part isn’t the story worth telling. What came out of it was a GitHub Copilot custom skill – a reusable file that captures everything the agent…

Read More Read More