A circle, not a stage. No slides, no answers prepared in advance.

Every team is quietly working out the same thing: if an agent produces the first version of the code, how does anyone become senior? The old path ran through writing bad code, having it reviewed, and feeling the correction. A large part of that path has just been removed, and most teams have not replaced it with anything.

This roundtable is for engineering leads, senior developers and the juniors living through it. We'll work through the questions honestly:

What skill is actually being lost, and is it one worth protecting?
How do you review code nobody on the team wrote from scratch?
What does a meaningful first year look like now, and what should we stop asking juniors to do?
Where does trust in a codebase come from when authorship is shared with a tool?
What are teams in this room already doing that works?

I'll facilitate and keep it moving, not lecture. My role is to make sure the quietest person in the circle gets heard and that we leave with a few things worth trying rather than a general sense of unease.