Here's the recording of the live conversation today about Red/Green indicators when coding with agents.
It's only available for 24 hrs!
youtu.be/mXSrDMczbjo
#ElixirLang
Bruce does not argue for vague mentorship. He names four trainable practices: shape the PR, read architecture, throw away code that does not fit, and layer prompts with real boundaries.
That is enough to start next week.
grox.io/blog/31-the-trainable-things
Bruce Tate's first live session is Thursday, June 11. Red/green indicators for AI-generated code: how to tell when the agent got it right without reading every line.
Free to attend.
Recording public for 24 hours.
grox.io/live
#elixirlang
Teams keep treating the junior problem as talent. Bruce's argument is harsher: the work moved up the stack, agents took the basics, and we kept teaching for the old job.
That is a training failure, not a hiring one.
grox.io/blog/31-the-trainable-things
Bruce Tate's first live session is Thursday, June 11. Red/green indicators for AI-generated code: how to tell when the agent got it right without reading every line. Free to attend. Recording public for 24 hours.
grox.io/live
#ElixirLang
AI tools improved faster than our ability to use them well. We treated the conditions that made it work as the new baseline, and organized our optimism, our staffing, and our planning around that assumption. That was wrong.
grox.io/blog/30-how-better-tools-can-make-things-worse
#ElixirLang
The cost of the AI productivity dividend is paid by humans, in three places. None of them are doing their jobs badly. They are doing exactly what their roles ask for, inside a system that has quietly stopped delivering.
grox.io/blog/28-the-sludge-on-the-wall
#ElixirLang
---
Most maintenance pain starts when one function reads input, makes the decision, prints the answer, and loops. Split the work into a functional core, a boundary, and a public API before the file grows around that mix.
grox.io/blog/29-building-in-layers
#ElixirLang
This is the shape: velocity up, judgment thin, juniors stuck, seniors flinching, dashboards counting the wrong thing. @redrapids.bsky.social names it, and names the pact every team has to make before the next sprint spends the dividend.
grox.io/blog/28-the-sludge-on-the-wall
#ElixirLang
The useful question is not where the code fits in the file. It is what kind of complexity the code carries. Rules belong in the core, the world belongs at the boundary, and the API keeps the two talking.
grox.io/blog/29-building-in-layers
#ElixirLang
