Why this site is called a cookbook

Let me get the pun out of the way first. My surname is Koch, which is simply the German word for cook. Translate it and you get Sebastian Cook, which is how this site got its name.

But the name is only half the reason I call it a cookbook. The other half is about what I want the writing to be.

A lot of technical blogs are someone thinking out loud. Useful, but you often cannot tell what actually worked from what the author only hoped would work. A cookbook is different. A recipe is something that has been made, tasted, and written down so the next person can reproduce it without the guesswork. That is the bar I want to hold here. If a post describes a solution, it is because I built it and it held up in production, not because it sounded good in theory.

So here is what a recipe on this site looks like. A real problem from a real project, stripped of client details. The approach I took, and why. The parts where it tends to burn, meaning the gotchas that cost me hours. And ideally something you can lift straight into your own work.

The menu leans toward the Microsoft Power Platform and Dynamics 365: solution patterns, consent and GDPR done properly, and AI with Copilot without cutting corners on data protection. Some recipes are full deep dives, some are quick notes for a single sharp problem. I would rather show range than pretend I only ever cook one dish.

That is the whole idea. Pull up a chair. The first proper recipes are already in the oven.