My talk with another Director of AI


The Applicable Bytes

Career & Growth, Technical leadership & AI for developers

In this email I reflect on my recent interview with another fellow "Director of AI", Courtney Kingsbury, and we talk about common problems, fears and challenges that adoption of AI brings in two different companies.

You might be the only person at your company who gets AI, then you already know the quiet weight that comes with it. Nobody above you understands what you actually do, nobody beside you can check your work, and every call you make, you make alone. What nobody warns you about is that there's no rule book for this job.

AI-Rule book doesn't exist yet, and you feel that every single day.

I know all of this because it's my job as well, and for a long time I quietly assumed I was doing it wrong. I had no one to compare notes with, so every decision felt like guessing in public and hoping nobody noticed.

Then I met Courtney, and it shifted something for me. She has the same job that I do, except she's doing it at a company about 30 times the size of mine, in an industry so regulated that one wrong move is a real problem. We got on a call and just talked for an hour, the way you can only talk with someone who does the same strange job you do, and the relief was almost funny. It's the same everywhere.

The same loneliness, the same quiet fear that you're doing it wrong!

The same two camps of people to hold together: the ones who think AI is a magic wand, and the ones who are sure it's useless. Your whole job, it turns out, is to stand between them and stay calm.

And here's the thing we both kept coming back to, the part that never makes it onto LinkedIn.

The hard part was never the technology. It's the people, and it's carrying all of it with no one around to tell you you're on the right track.

So we said the quiet things out loud. We talked about the AI your team is already using that you can't see, and why that should scare you a little. She told me why she says no to tools people practically beg her for, and why "approved" never means "safe forever." And we got into the part nobody mentions, which is that this role, precisely because nobody has defined it yet, lets you basically invent your own job.

If you're thinking about becoming the AI person where you work, this is the conversation I wish someone had handed me three years ago. And if you already are that person, and some days it feels lonely, the one thing I want you to hear is this: you're not doing it wrong. There's just no map yet, so we're sitting down and drawing one, out loud.

I'd love for you to watch the whole thing:

Postboks 60, Bergen, Vestlandet 5821
​Unsubscribe · Preferences​

Dalibor Jovic

I help lonely developers, technical and AI leaders with their career and with AI adoption. Once every few weeks I send an email about AI adoption, good coding practices and personal development.

Read more from Dalibor Jovic

The Applicable Bytes Career & Growth, Technical leadership & AI for developers A few minutes into my conversation with Anders Dræge, I realized something slightly embarrassing. He has won awards for his AI work. The last award I remember winning was for school electronics, somewhere around eighth grade. And the difference between us isn’t the technology. Anders leads AI development at Frende Insurance in Norway. His AI systems run in production, and together they save over 400 human hours a...

The Applicable Bytes Career & Growth, Technical leadership & AI for developers You can have 100 projects of five years of experience in one company, and still not be senior. Because repetition is not the same as growth. That sounds obvious when you read it. It was not obvious when I lived it. After five years of programming, I looked strong, on paper: around 100 projects, a team lead title, and forum administrator credibility from the old PHP days. Those things helped me get my foot in the...

The Applicable Bytes Career & Growth, Technical leadership & AI for developers 20 years have passed since I got paid to code for the first time. Here are few things I’ve learned along the way. Most programmers think a career grows with time. Get a job. Complete projects. Stay long enough. Become senior. I did that. I worked on around 100 projects, became a team lead, moved to Norway, and arrived confident that my experience would open every door. Then I discovered I was a junior developer...