Copilot

This month at Stir Trek 2025, I presented on Dev Containers and GitHub Codespaces, demonstrating how these tools streamline both local and cloud-based development workflows. The session covered the essentials of creating portable development environments, customizing containers with features and extensions, and launching Codespaces directly from your repository. A lively Q&A followed, with attendees asking about strategies for running and working with multiple containers. Below, I’ve distilled those discussions and provided a deeper dive into shared container configurations across multiple projects-including folder structures, Docker Compose setups, VS Code workflows, and advanced tips you can apply in your own work.

Rubber Duck Debugging in the Age of AI # Ever found yourself explaining your code to a little rubber duck perched on your desk? If so, you’re in good company. This quirky practice, known as rubber duck debugging, has helped countless developers articulate problems and discover solutions. The idea is simple: by forcing yourself to explain your code, line by line, to an inanimate duck, you often stumble upon the bug or insight you needed. It’s like having a silent pair programmer who patiently listens as you work through the logic. But what if your rubber duck could talk back and offer suggestions? Modern AI coding assistants (like GitHub Copilot) are becoming the new interactive rubber ducks, and that means a lot for debugging, brainstorming ideas, and reviewing code.

I had a real world example today that I wanted to share about copilot helping me with a coding problem. A friend reached out asking if I knew regex. Its been a bit, but I was happy to help because I thought we could figure it out.