Many developers are already using AI. But here’s the thing: most of them do it in secret. They test it in side projects, use it quietly to get through tickets, and then draw conclusions—without ever bringing it into the open with their team.
That’s a mistake.
When I’ve been disciplined in my own work, I noticed something: I was faster, could work longer, and felt less drained, because I stayed focused on high-level thinking instead of every small detail. That’s precisely the kind of shift AI can support.
But here’s the danger: if you let AI turn into a lazy habit, if you’re just vibing with it instead of working with intention, the outcomes get worse. You’ll ship sloppy code, misunderstand problems, and create more cleanup work later. At scale, that kills quality and trust.
And if AI use stays a private habit, it doesn’t scale anyway. Worse, it creates hidden workflows, uneven quality, and mistrust inside the team.
The solution is simple: treat AI as a team strategy. Not a secret shortcut. Not a personal experiment. A shared challenge. Align on how to use it, where it makes sense, and what it should not do. Explore it together.
That’s when AI becomes valuable: when it creates space for humans to do what we’re best at—thinking, designing, and solving problems—without burning out on the repetitive parts.
—Adrian
Share this post