Jason St-Cyr

I went through the State of #DevOps report and I have... thoughts. I still need to crystallize some of my opinions on what I saw in this report, but I was interested in the heavy correlation between "mature DevOps" and "AI successful". I'm not surprised. AI tools work best with structured processes, lots of data, plenty of tooling it can gain access to. If everything is chaotic, one-off, manual stuff... that doesn't give much room for gains from an AI tool. (1/2) https://www.perforce.com/resources/state-of-devops

I have been banging my head against GitHub copilot trying to figure out why it wasn't following the instructions I'd given it. Asking the MCP why it didn't follow them was no help, it simply told me it should have and made unnecessary changes to my instructions files which it then also ignored. The clincher was .github\copilot-instructions .md As somebody learning about Copilot instructions, everything I read was about how to create your own instructions in the `instructions` subfolder, but what I didn't see was that if you don't tell agents that the custom instructions file exists with some sort of mapping in the default copilot-instructions file, the agents don't even go looking for it. This one line in that MD file did the trick: See [puppet-instructions .md](.github/instructions/puppet-instructions .md) for Puppet development guidelines. So I share with you, in case you too have been trying to learn this and didn't know.