Introduction The first time I started seriously using AI in my DevOps workflows, I made the same mistake I've seen many others make. I treated it like a tool. Something you prompt, get an answer from, and move on. It worked, to a point. But the results were inconsistent. Sometimes surprisingly good, sometimes completely off. It felt less like working with a system and more like rolling a dice. That changed when I started thinking about AI differently. Not as a tool - but as a junior platform engineer joining the team. That shift alone made everything more predictable. The First Day Problem When a new engineer joins a team, we don't expect them to be productive immediately. We don't just hand them access to production systems and ask them be productive. Instead, we onboard them. We give them: context about the system documentation boundaries a safe environment to contribute time to understand how things work Without that, even a talented engineer will struggle. AI is no different.…