I go to Krav Maga also and sometimes we're going pretty hard and fast striking repeatedly. It can be so tiring, but I find I can enter a zone where I am breathing deeply and slowly while going even faster or harder after I've noticed that I'm tired.
Probably summed up with "Breath Work".
I use GitHub CoPilot everyday. I usually limit it to a fancy auto-complete. It's really helpful for repetitive refactor tasks, I just have to go to each line and it updates. This way I still see what's happening, but it is faster than manually making those changes that can't be solved with a find and replace.
Sometimes I fight CoPilot because it will continue to suggest something I do not want to do. In those instances I code faster as to outpace the AI's latency.
Other devs are building MCP servers to help access our tools for AI integration. Devops seems heavy on spec driven and test driven development through AI. The spec driven development looks interesting, but a bit of overhead to get started.
Our company has an AI first directive right now where we're supposed to use AI for everything and see what works. I somewhat disdain it, but it's also fun to have a directive to try new things indiscriminately (using AI). The more I drink the Kool aid, the better it tastes.
As an engineer, development still comes down to requirements gathering, solid engineering principles, and the tools we already have at our disposal - network calls, rendering the UI, orchestrating containers and job, etc.
All that is to say that I thought AI was going to be sexy, like Westworld, and not so boring...