What if your repository could triage issues, investigate CI failures, and update documentation without you? GitHub just launched Agentic Workflows – a new way to automate repository tasks using AI coding agents, all written in plain Markdown. Here’s a look at how they work, what makes the security model interesting if you work with AI, and why you should pay attention.

Have you ever watched your AI assistant suggest something completely different from what you expected? Ever had it seem to ignore clear step-by-step directions and do something different? I was frustrated when Copilot kept making inconsistent decisions about my content metadata. After trying custom instructions and task-specific prompts, I finally found the solution: give the AI exactly what it needs. Here’s how I did it.

Ever notice how AI assistants are brilliant at reasoning but can’t actually check your database or call your APIs? You end up playing middleman, copying data back and forth. Model Context Protocol (MCP) changes that. It’s an open standard that lets AI assistants connect directly to your data sources and tools while keeping you in control. Let me show you more about what it is, how it works, and why it matters.

While AI tools like GitHub Copilot are revolutionizing software development, they’re not replacing developers—they’re amplifying them. Learn why companies that think they can eliminate developers are making a costly mistake, and how the smartest organizations are using AI to make their teams faster and more effective than ever. And learn how you and AI will be working together to create even more value.

It’s becoming increasingly important to understand how AI tools work. Sometimes, the way you prompt the model can drastically alter the response generated. With a little effort, it can even enable a model to request information from external APIs or tools. In this post, I explain how prompts can be used to enhance the response generated by AI models by interacting with tools and APIs.