My starting point with generative AI was fairly ordinary: refining emails and expanding rough ideas.
Then I saw AI agents being used for coding. My first reaction was "That's interesting, but not for me". It looked far from my day-to-day work.
Still, it changed the next question I asked.
Once I was already using AI to summarize responses, the next question was whether it could turn that content into an Excel sheet.
The answer was yes, but with limits. The tool I was using could generate a file, but if I wanted changes, it often created a new version instead of editing the original.
That was the point where I started asking a different question: can this work with files directly?
From there, I learned more about agents that can work with local files and make changes step by step.
Around the same time, I started to see Git differently too. Git had always felt slightly outside my usual work. Over time, I started to see where it could support my own content process, especially on projects where versioning and collaboration matter.
Getting set up did take some help. But seeing what was possible first meant I could ask more focused questions when I needed support.
That's when possibility started to become practice. The tools weren't just interesting to watch. They had a place in my own work.
This blog reflects that shift too. A lot of the workflow behind it came from one simple question: "Wait, can I use this?"
Over time, the questions start to change. You stop asking whether something is meant for you and start asking what you can do with it.