Rod Johnson

The first of a series of blogs showing how AI agent examples from popular Python frameworks can be rewritten in Java to be far better, using Embabel. Today's target: CrewAI. @springrod/you-can-build-better-ai-agents-in-java-than-python-868eaf008493" target="_blank" rel="nofollow noopener">medium.com/@springrod/you… #embabel @java @crewAIInc @rseroter @gsaab @starbuxman @JamesWard @springboot

Looking forward to talking to the NYC Java community next Wednesday about Embabel and the role of the JVM in Gen AI @java @springboot eventbrite.com/e/building-sma…?

Enterprise AI ist kein Prompt Engineering. Sobald AI Teil realer Systeme wird, geht es um Architektur, Integration, Governance und reproduzierbare Systeme. Ein guter Einstieg: die W-JAX Opening Keynote von @springrod. f.mtr.cool/pvniltdqem #EnterpriseAI #AIEngineering

@staleksit Try Discord. Link in main repo

I don't want to bother you too much, just wondered if there is some official communication channels (for Q&A)?

Hey @springrod I've started looking into Embabel framework for some PoC of mine. Managed to replicate first demo "WriteAndReviewAgent" example and it's working. Yeeey 🥳 Anyway, at the moment I have question - based on UserInput I rarely get that crafted Story is matching theme.

@brunoborges @lucas_montano And currently design is the problem…there may not be bugs (yet) but without oversight, coding agents tend to grow codebases in a haphazard way, so they degrade fast

@lucas_montano Man, if we don't review code written by AI, then what accountability do we even have?

we need to admit defeat we won’t be reviewing code before it goes to production humans are already the bottleneck

@mkurman88 True but using other projects as references helps a lot, and also closely directing design throughout

After two months of heavy "coding" with AI agents, I have one conclusion: if your codebase already exists, is fully human-written, and you use agents to add or improve features, it works great. However, when you try to create something new from scratch, they tend to add so much overcomplicated spaghetti code that it's hard to maintain in the long run. No matter which coding model you use, sooner or later, you'll hit a wall you can't break through.

I thought I was over this meme but this is the funniest one I’ve seen

And now, @springrod on Enterprise challenges for AI at @devnexus I've said it before, yet. I'll say it again: @springrod 's take on AI is one of the most clear, refreshing and developer focused messages I've seen out there. Doing AI? You better at least know what he is saying.

Just watched this. Nice example of Embabel!

Fun new blog from Embabel engineer Jasper Blues about the Embabel guide chatbot - both a resource to help develop with Embabel, and an example of Agentic RAG against Neo with both vector/text search: medium.com/embabel/the-vo… @java @springboot @neo4j

@Ken55172479 @JavaAtMicrosoft @starbuxman @brunoborges @grok Java is bigger than any one company

@JavaAtMicrosoft @springrod @starbuxman @brunoborges Isn’t Java an oracle product? Why jdconf is related to Microsoft @grok

The #JDConf 2026 agenda is LIVE! Learn how to build agents in #Java, ship faster with agentic DevOps, and modernize apps at scale. Free, virtual, April 8-9. 35+ speakers, 3 livestreams. Register → jdconf.com Featuring @springrod @starbuxman @brunoborges

@shanselman Infuriating, isn’t it. What human actually wrote like that??

"just dropped" "killed every ____ with this one simple" "absolute game changer" "here's the real unlock" "this 20 line md skill changes everything"

@oilersbluesky @javainterviewer Daniel is correct. The post is nonsense

@javainterviewer I think this is bs. Spring was based off @springrod's J2EE book (I started using it from that books sample code). Singletons were core concept of dependency injection since before Spring was even Spring

Something interesting I learned today related to Java Spring boot Why does Spring by default create beans as singletons? Actually, this is a historical bug! Initially, Spring created a new bean for each request, but one of the developers forgot to add new in the loop, and all beans became singletons. Now this is called a feature for compatibility with legacy code! Holiday fact: If you add @Scope("christmas"), Spring will create a new bean only on December 31st! Ideal for seasonal promotions! Why is singleton the default: → Performance: creating an object is an expensive operation (memory allocation, constructor call, DI). Creating a bean for each request is a huge overhead. → Management of system resources: Many beans encapsulate operating system or network resources, which are expensive to create and should be shared. → A natural model for stateless components: 90%+ of business logic in Spring is stateless operations. Creating a new object for each call is meaningless. → Resource savings: one EntityManager, one RestTemplate, one connection pool → Caching: the bean can safely cache data (if it's read-only) → Simplicity of the life cycle: @PostConstructwill be executed once

Looking forward to my first dev/nexus. See you in Atlanta next week! My keynote will be about how to make Gen AI reach its full potential in enterprise, by building on what already works. Viewing this as a greenfield problem is a recipe for failure @java @spring #Embabel

@ivangsa It’s a valuable tool. I use LLMs to help with research and drafting. But fundamentally the final form reflects the author and should be in their human voice

@springrod We are learning in the process. I publish articles in a popular spanish tech blog, and they edit the articles with LLMs, adding table of contents, references.. typos, etc... Seemed like a good idea, now I feel ashamed of some articles. Thinking to request adding a disclaimer 😓

So much LLM writing is so annoying, and so easy to spot. This is the messy reality no one is talking about. Let that sink in.

@ASpittel Nothing original here. #Embabel does the same thing wrt function/method signatures, as well as incorporating them in sophisticated type-driven workflows. Yes, types are critical, as is close interop between model calling and language constructs. #complete-example" target="_blank" rel="nofollow noopener">docs.embabel.com/embabel-agent/…

I think every dev is thinking about what the future of code is right now. Yesterday, AWS shipped an experimental Python library, AI functions which behave like standard Python functions, but are evaluated by reasoning AI Agents. Check it out! github.com/strands-labs/a…

Strong tests have always been important. With coding agents they are even more important as a fitness function: - "Keep working on [whatever] until test X passes. Do NOT change the test" Important to ensure the agent doesn't just take a shortcut by removing assertions

@ronnieschaniel It feels disrespectful to the reader. If the author didn't care enough to put the effort in to get rid of the cliches, I'm not inclined to endure them. And did the author read it and check it properly?

@springrod I've read blog posts and even books where you could recognise the LLM writing clearly. A bit depressing.

@narahari Plain writing. It's an invaluable tool for code gen, although human oversight remains crucial

@springrod As in code generation or just plain writing?

AI should grow out of your application, not land on it from space Memory must be grounded in existing structured data Free-form text is not enough. Introduce as much structure as possible & link to existing data @springrod/agent-memory-is-not-a-greenfield-problem-ground-it-in-your-existing-data-9272cabe1561" target="_blank" rel="nofollow noopener">medium.com/@springrod/age… #embabel @java @springcentral @kotlin