Github Will Prioritize Migrating to Azure Over Feature Development

But since “new features” consists primarily of shoving the bloody copilot agent down everyones throat, it might not be such a bad thing.

Before that, it still felt like there _some_ degree of autonomy and ability to think about the developer experience on the platform as a whole. Once ChatGPT took off and MSFT decided that they were going to go hard on AI, though, Copilot (and therefore GitHub) became too important to Microsoft to leave alone.

I kinda suspect the slide was inevitable anyway, given how acquisitions tend to go. But IMO, Copilot was the tsunami that washed the octocat out to sea.

The realization that you're close to making, and I hope I can help you make: If Microsoft & Github can't realize the benefits of AI that quickly; why should anyone believe that the rest of the world would be able to? After all, there are roughly zero "pre-AI" companies that are force-mutating their structure to adopt AI faster than Microsoft is [1].

[1] https://www.theverge.com/tech/780946/microsoft-satya-nadella...

IIRC in the paper itself they back up their reputation using their previous predictions that only had a ~50% success rate.

I also just don’t know why the paper needed to make up narrative stories as predictions instead of being more straightforward.

I think there will probably be a long tail which will prevent that from happening so quickly.

(It also probably doesn't really matter... if their main goal is to scale using azure they really only need the stuff that will be scaling up to be there. They probably also want to be seen as eating their own dog food, which can reasonably be achieved without all of the long tail.)

You can pair that up with a template repository for the org and everyone can start new projects from that template (which contains the workflow to check future workflow files).

If you want assistance with organisation-wide code policies, I can help and my email is in my profile.