AI can already write AL code, troubleshoot errors, and draft documentation. So what's left for you to be good at?

This session is about using AI well without losing the skills that make you good at your job. It's built around three ideas: Adopt, Adapt, and Stay Human.

We'll start with Adopt. The question isn't whether to use AI, it's how to use it without creating problems you'll pay for later, especially as AI starts producing more code and documentation than any team can follow.

Then Adapt. The tools keep changing shape. Prompt engineering became context engineering almost overnight, and something else may replace that too. We'll look at the underlying skill that doesn't change, and the difference between developers who keep starting over and the ones who keep getting better, no matter what tool or budget they're handed.

Finally, Stay Human. As AI gets better at the technical side of the job, what actually makes you valuable starts to shift. We'll talk about what that advantage looks like, and why it's something no agent can replace.

You'll leave with practical habits you can use in your own BC work this week, and a clearer sense of what actually makes you valuable as AI gets better.