Ep86: AI Workflow Realities + Architecture Trade-offs

I'm back after some time off and excited to catch you up on everything that's been happening. This week, hear updates on the Java book, some upcoming fall events, and dive into two articles that challenge how we think about AI in development and architecture.

• The Java book is in its final chapters. It now incorporates Claude, planning mode, and a capstone project so developers walk away with something personal and useful
• Feeling out of touch with the industry's pace? Me too! Balancing competing priorities is a real challenge
• Fall events ahead: Java User Group tours (East Coast in September, Southeast in November), plus new guest episodes and 2027 conference abstracts
• Article 1: "You Need AI That Reduces Maintenance Costs" by James Shore. AI boosts front-end productivity, but what about long-term maintenance costs?
• Maybe we should "shift right" just a bit — plan for your future self, not just immediate output
• Article 2: "AI versus Microservices" by Michael T. Nygard. AI tools speed up development but cause merge conflicts, governance gaps, and ownership sprawl
• The monolith vs. microservices debate extends beyond tech. Streaming services and cloud backups follow the same pendulum
• More data points lead to better architecture decisions, whether in AI processes or everyday life

Thanks for listening, and happy coding!