Written By Barry Crowell 

I kept seeing “vibe coding” pop up all over the internet, and honestly, I was skeptical. Another buzzword? But curiosity won, so I fired up VS Code with GitHub Copilot and decided to test it out. 

My challenge: build an iOS game mixing Asteroids and Space Invaders. The catch? I’d never touched Swift or SwiftUI before. Yet somehow, I had a working game up and running faster than I expected. No syntax errors. No endless Stack Overflow tabs. Just me describing what I wanted and Copilot making it happen. 

I wasn’t writing code anymore. I was architecting ideas. “Add power-ups.” “Make the asteroids split when destroyed.” “Speed up enemy ships after level three.” Copilot handled the implementation while I focused on the creative vision. It felt less like programming and more like collaborating with a developer who never gets tired or frustrated. 

Cool experiment, right? But then I realized something: if this works for a game I built for fun, what could it do for my actual job? 

Bringing It to Real Consulting Work 

As a Power BI and Dynamics 365 consultant, I spend a lot of time in T-SQL. Many clients still run legacy on-premise implementations of D365 Sales and Dynamics GP. When something breaks in those systems, I need to fix it fast. 

The old way of troubleshooting SQL was painful. Dive into stored procedures written five years ago by someone who left the company three years ago. Hunt for documentation that doesn’t exist. Trace through complex logic trying to figure out where things went wrong. It worked, but it ate up hours. 

Now? Completely different story. 

My New SQL Troubleshooting Process 

Here’s my workflow now: 

I connect to the client’s VPN and open their SQL Server through the VS Code extension. Find the problem code causing the issue. Then instead of manually tracing every line, I just tell Copilot what’s wrong in plain English. 

“This stored procedure is double-counting commissions for split sales” or “Why is this query taking 45 seconds when it should be instant?” 

Copilot analyzes the code and points out the likely problems. Missing index. Bad join logic. A WHERE clause that’s forcing a table scan. It doesn’t just identify issues either; it suggests the actual fixes with explanations. 

I test the changes, validate the results, and push the fix. What used to take half a day now takes an hour or less. 

What This Actually Means 

Vibe coding isn’t about letting AI write all your code while you sit back. It’s about changing your role. You become the architect and quality controller instead of the person typing every semicolon. 

I can now work across technologies I’m not an expert in. I can solve problems faster because Copilot has seen patterns across millions of code examples. I spend less time on syntax and more time thinking about what actually needs to happen for the client. 

The human part is still critical. I make the decisions. I understand the business requirements. I validate that solutions actually work and make sense. I communicate with clients and think strategically about their systems. 

But the mechanical stuff? The “how do I write this join” or “what’s the syntax for that function” questions? That friction is just gone. 

Why You Should Try This 

If you work with Power Platform, Dynamics 365, or any enterprise tech stack, experiment with this approach. Pick a small project outside your comfort zone like I did with that game. See what it feels like to describe what you want instead of getting stuck in implementation details. 

Then bring it back to client work. You’ll probably find you can diagnose issues faster, implement solutions quicker, and deliver more value without burning out on tedious troubleshooting. 

The future of consulting isn’t about memorizing every API or syntax rule. It’s about knowing how to guide AI tools to execute your vision while you maintain the oversight and strategic thinking that clients actually pay for. 

After going from building Asteroids to fixing production SQL bugs, I’m convinced vibe coding isn’t just a trend. It’s a genuine shift in how we solve technical problems. And honestly? It makes the work more interesting and less frustrating. 

The tools are here. They work. Now it’s your turn to see what they can do for your consulting practice.