Groxio
@groxio
Master Elixir with expert-led courses covering AI, LiveView, OTP, and more. Mentoring, team training and video courses from Elixir expert Bruce Tate. Grox.io
Today at 12 EDT! register grox.io/live See when LiveComponent still fits, when explicit state flow is the better default, and how to encode that decision in a skill. #Elixirlang
A short clip from the last @redrapids.bsky.social Groxio Live on July 9th. Join us for the next one: LiveComponent Replacements and Skills on Thursday July 23rd! 12 EDT. grox.io.live #ElixirLang
The old junior apprenticeship taught through typing volume. Agents changed the work. Now the skill is judgment: shaping scope, reviewing structure, preserving prompts, and knowing when generated code should be discarded. Read the blog: grox.io/blog/39-codi...
Don’t eat the seed corn! An excerpt from Bruce’s Groxio Live last week. #elixirlang #AIEngineering
Bruce Tate Live starts in 1 hour. Topic: five ways programmer training changed in 2026. If you registered, check your email for the join link. grox.io/live
Bruce Tate goes live tomorrow at noon ET. Topic: five ways programmer training changed in 2026. Generated code, architecture, review signals, judgment, and production tradeoffs. Free. register: grox.io/live
The junior developer's job did not disappear. It moved from writing first drafts to directing and verifying them. New blog from @redrapids.bsky.social grox.io/blog/37-the-...
A pure functional core gives the model less ambiguity to resolve. That means cleaner tests, a clearer API, and fewer mistakes hiding at the boundary. grox.io/blog/36-design-for-ai-why-pure-functions-make-better-ai-partners
`@doc` is not a prettier comment. In Elixir, documentation is module data that IEx can read, ExDoc can publish, and ExUnit can test. Write the example you would type in IEx, then let `doctest` keep it honest. Read the blog! grox.io/blog/35-your... #ElixirLang
Bruce Tate goes live tomorrow at noon ET. Topic: is the junior developer career path dead? What changes when juniors work with AI from day one. Free. grox.io/live
Bruce Tate Live is this Thursday, June 25. Topic: is the junior developer career path dead? Noon ET. Free to attend live. Register: grox.io/live #ElixirLang
Claude can write a clean architecture plan. That does not make it trusted architecture. Bruce caught a Phoenix auth mistake that looked reasonable and carried security risk. New Blog - grox.io/blog/33-the-... #ElixirLang
The codebase is no longer the scarce asset. Judgment is, and judgment lives in people. @redrapids.bsky.social on the structural moves that turn juniors into the seniors you will need later. grox.io/blog/32-how-juniors-become-seniors #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
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
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 ---
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
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
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
Lots of energy at @redrapids.bsky.social training today @elixirconf.bsky.social EU! Thx for the photo @paulovalim.bsky.social #ElixirLang
This Master Class is about structured prompting, architectural patterns, and proper oversight. It's about building production-ready systems with AI, not letting AI generate whatever and hoping it works. You are in charge, not the agent. Learn with @redrapids.bsky.social codebeamvancouver.com
Hey! We'd love for you to be with us and there's a Valentine's Day discount going on now for tickets to the conference! Buy one, get one! codebeamvancouver.com #ElixirLang
Function Heads are Chosen By Shape Full blog post: grox.io/blog/13-func... #ElixirLang
New Blog Post: Stop Prompting and Start Anchoring Read it here: grox.io/blog/12-stop... #ElixirLang