The Risk of Banning AI at Work

Joris warns that forbidding AI drives shadow usage and increases data leakage and security risks.

Play episode from 03:55

chevron_right

Transcript

chevron_right

Transcript

Episode notes

We are at a unique point in history where there is finally an alternative to human coding. If AI can write the code effectively, what is left for the software engineer?

In this episode, Joris Conijn (AWS CTO at Xebia) argues that the era of "just coding" is over. We discuss why senior developers are safe (for now), why juniors are at risk of never learning the fundamentals, and how "Shadow AI" is forcing companies to change their security strategies.

Most importantly, we break down the difference between a "Programmer" and a "Software Engineer" with the introduction of agentic tools. If you want to future-proof your career and move from writing lines of code to designing systems, this conversation is for you.

In this episode, we cover:

Why banning AI at work actually increases your security risk
How to use AI to automate the boring parts of the SDLC (requirements & user stories)
The critical difference between "Coding" and "System Architecture"
Why you should check your AI Agents into your Git repository
The 20-year problem: what happens when engineers never learn the fundamentals?

Connect with Joris Conijn:

https://www.linkedin.com/in/jorisconijn

TIMESTAMPS

00:00:00 - Intro

00:01:11 - What Keeps a CTO Excited About Tech?

00:02:58 - Stop Being the "Department of No" in Security

00:05:28 - The Real Risk of Banning AI at Work

00:06:32 - When Developers Hold the Organization Hostage

00:08:14 - The Hidden Dangers of Instant AI Code Fixes

00:09:50 - Will Future Devs Understand Object Oriented Programming?

00:11:36 - Using AI to Accelerate Learning vs Copy-Pasting

00:13:17 - Why Testing Matters More When AI Writes Code