Bruce Tate Live

Engineering conversations, every other Thursday.

Bruce takes the topics from his AI Crises Series and his Groxio training work and turns them into 60-minute live sessions. Real questions, no slides, no script. The kind of room where engineering managers and senior engineers think out loud about what AI is doing to the work.

Free to attend. Recorded for subscribers. 1st and 3rd Thursdays.

No spam. One email per scheduled session with the join link. Plus the occasional recap of the previous one.

Bruce Tate

First sessions

Session 1

Red/Green Indicators: how to tell when the agent is wrong

June 2026 (date TBD)

Session 2

Is the junior developer career path dead?

June 2026 (date TBD)

Coming up

The first two sessions are scheduled. Topics are pulled from real conversations with engineering teams Bruce works with.

Session 1

June 2026 (date TBD)

Red/Green Indicators: how to tell when the agent is wrong

The quick inspection points that let a reviewer judge AI-generated code without reading every line. Where in the diff to land your attention first. What fits this codebase looks like in 30 seconds. The exact red flags that mean throw it away and ask again. Live, with real PRs.

This is the senior-review work the AI Engineering Enablement training teaches — condensed into one session.

Session 2

June 2026 (date TBD)

Is the junior developer career path dead?

The industry's answer is hire fewer juniors. Bruce's answer is the opposite: train them. This session walks through what changes when juniors operate at architectural level on day one, what's actually teachable, and what an org has to do differently to grow the seniors of 2030.

Same argument as the How Juniors Become Seniors essay — but live, with team-specific questions.

Coming next — topics in the queue

Pulled from the same well as Bruce's article series and the team-training engagements:

  • What throw it away actually looks like in a real PR

    The discipline, the conversation with the author, and the team norms that make it stick.

  • Functional duplication: how to find it without an AI auditor

    Quick scans, naming patterns, and the seams where drift hides.

  • IoC seams under AI pressure

    Protocols, behaviours, dependency injection, and the architectural work agents can't do.

  • Prompt layering as software design

    Composing prompts the way you'd compose modules.

Sign up above to get notified when each one is scheduled.

Why these sessions exist

"I write the essays. Then I sit with engineering teams and the same questions come up — red/green indicators, what's worth throwing away, how to grow juniors who can do this work. The lives are that conversation, in public. People who show up are usually halfway to the answer; they just haven't said it out loud yet. The room helps them get there."

— Bruce Tate

These aren't webinars. They're not pitches. They're a small public version of the work Bruce does inside engagements — and they're free because the conversation tends to be more useful than anything we'd charge for.

Bruce Tate

About Bruce Tate

Bruce is the author of more than ten programming books, including Seven Languages in Seven Weeks, Programming Phoenix, and Designing Elixir Systems with OTP. He's been training engineering teams for two decades. He runs Groxio, a teaching company focused on Elixir, OTP, Phoenix, LiveView, and the discipline around AI-assisted engineering.

The live sessions are an extension of the AI Crises Series — same audience, same questions, more room to think out loud.

For engineering managers attending these

If your team is feeling what Bruce describes in these sessions, the conversation extends naturally.

AI Engineering Enablement is a private 3–4 day intensive plus ongoing advisory for engineering teams adopting AI on real Elixir codebases. It is the training that the live sessions are condensed from, scoped through a diagnostic conversation.

The first step is a short conversation. No pitch deck, no proposal up front. We look at your team's current Elixir experience, AI usage, review bottlenecks, and architecture concerns, then decide together whether private training is the right fit.

FAQ

How often are the live sessions?
Every other Thursday — 1st and 3rd of each month. About 12 sessions per year. We may expand to weekly if other speakers join.
Are they recorded?
Yes. Recordings go to subscribers within 24 hours. If you can't make the live, you don't miss it.
How long are they?
60 minutes. Bruce talks for about 20–25 minutes, then it's questions from the audience for the remaining time. The Q+A is usually the best part.
Do I need to know Elixir?
The Mode B topics — review workflow, junior development, AI in engineering teams — are mostly language-agnostic. Elixir-specific topics come up too, but Bruce calls out which sessions are which.
Is this for individuals or for teams?
The audience is mostly engineering managers, CTOs, tech leads, and senior engineers. Individual developers who follow Bruce's writing also attend. The conversation suits both, but the prescriptions are org-level.
Is this affiliated with Gig City Elixir?
Bruce is a co-organizer of Gig City Elixir, and many of these topics overlap with what GCE covers. The live sessions are a Groxio program, not a GCE program — but if you came in through the GCE community, welcome.
Can I suggest a topic?
Yes. Reply to any session notification email with a topic you'd like Bruce to cover, and it might end up in the queue.

Ready?

Get a notification when each session is scheduled.

No spam. One email per scheduled session with the join link. Plus the occasional recap of the previous one.

We respect your privacy. Read our privacy policy .