This week, I co-led a two-day GitHub Copilot hackathon with a Microsoft customer.
The question that drove the entire event: how do we standardize software development within our org when the AI is non-deterministic?
In this post, I break down the new features you can incorporate today, based on recent advancements from GitHub, to bring consistency to AI-assisted engineering.
What stood out was not just how fast teams could build. It was how quickly things became inconsistent when every developer rely on personal prompting habits.
For example, One developer’s Copilot generates tests for every function. Another skips testing entirely.
One team receives code that reused the shared auth module. Another ended up with a custom, hand-rolled auth flow.
One developer’s output followed established naming conventions. Another produced code that looked like it came from a completely different codebase.
That is the real problem.
As AI becomes part of software delivery, teams need a better way to standard…
