Explore my posts

Logging is the first and most important part of running an API in production—but most developers either log too little or too much. In this post, we walk through setting up Serilog, capturing meaningful logs, redacting sensitive data, and enriching logs with context like order IDs.

You’ve been forced to maintain a poorly written legacy app; spaghetti code, no tests, and every new feature breaks two existing ones. Team morale is at rock bottom. New features take forever to ship. Regression bugs are constant. You gather your arguments and head to management. You: We need time to refactor. Management: What are you talking about? You: Let us refactor. We’ll ship faster, with fewer bugs, and engineers won’t want to quit. I can do it. Management: ...Okay. Now comes th

Stop settling for vague, hard-to-navigate API docs. In Part 2 of our 'Production-Ready APIs in .NET' series, we show how to transform your OpenAPI spec into a polished, professional contract using Swagger. See how thoughtful versioning and task-based design make your endpoints easier to use, easier to test, and easier to love.

Not all APIs that compile and pass QA are well-designed. In this post, we unpack a deceptively simple .NET controller and highlight the subtle flaws that hurt developer experience—then show how to redesign it using clear, task-based endpoints and proper documentation.