Rod Johnson

5.4K posts

Rod Johnson banner
Rod Johnson

Rod Johnson

@springrod

Building the future of agent frameworks at Embabel. Creator of Spring. Developer, Entrepreneur, Investor, Author. https://t.co/IBqJ1rMmFe

Sydney / Bay Area Katılım Nisan 2009
807 Takip Edilen34.2K Takipçiler
Rod Johnson retweetledi
Cult.Repo
Cult.Repo@CultRepo·
🇬🇧London friends! Join us for the live premiere of Spring: The Documentary on May 7th at @DevoxxUK. The event is open to DevoxxUK ticket holders and the public, register for your free ticket before they go! Register here 👉👉luma.com/xv1iva0d Spring: The Documentary traces the full arc of one of open source's most consequential projects: from its origins as a quiet rebellion against enterprise Java complexity, through the paradigm shift of Spring Boot, into the microservices era and the cloud-native architectures that now run beneath some of the world's most critical software. Watch the trailer here youtube.com/watch?v=4qTwA6… After the film, there will be a panel featuring some of the cast, who will discuss the history of Spring and the making of the film @starbuxman, @MaritvanDijk77, @spoole167 ​Doors open at 6:30pm ​Film starts at 7pm ​Panel at 8pm The film features: @springrod @springjuergen @rstoya05 @markpollack, @sdeleuze , @starbuxman @snicoll, David Sayer, @scottyfred, @spoole167, @MaritvanDijk77, @MarcoBehler and @sergialmar Big shoutout to our incredible sponsors @herodevs and @jetbrains
YouTube video
YouTube
English
2
7
19
1.2M
Rod Johnson retweetledi
Cult.Repo
Cult.Repo@CultRepo·
Spring: The Documentary arrives 7th May! 🍃 Spring didn’t start as a framework, it started as a reaction to complexity in enterprise Java. What followed was a movement that redefined how modern applications are built, from Spring Boot to the cloud era. This is the story behind one of the most influential technologies in software.
English
3
42
160
16.8K
Rod Johnson retweetledi
Josh Long
Josh Long@starbuxman·
Happy belated birthday! @springframework’s BeanFactory turned 25 years old on Monday
Josh Long tweet media
English
5
16
132
7.3K
Rod Johnson
Rod Johnson@springrod·
Nice blog by Embabel's Jasper Blues using Embabel for AI and Neo4j graph to analyze project dynamics "Let’s see if we can use 1970s network science to predict future forks, governance crises and other notable schisms on GitHub projects." @neo4j @kotlin medium.com/embabel/factio…
English
1
1
10
2.1K
Rod Johnson retweetledi
JAX
JAX@jaxcon·
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
JAX tweet media
Deutsch
0
2
1
732
Alex Stoisavljevic
Alex Stoisavljevic@staleksit·
I don't want to bother you too much, just wondered if there is some official communication channels (for Q&A)?
English
1
0
0
20
Alex Stoisavljevic
Alex Stoisavljevic@staleksit·
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.
English
1
0
0
66
Rod Johnson
Rod Johnson@springrod·
@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
English
1
0
4
166
Bruno Borges
Bruno Borges@brunoborges·
@lucas_montano Man, if we don't review code written by AI, then what accountability do we even have?
English
3
0
18
2.4K
Rod Johnson
Rod Johnson@springrod·
@mkurman88 True but using other projects as references helps a lot, and also closely directing design throughout
English
0
0
1
270
Mariusz Kurman
Mariusz Kurman@mkurman88·
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.
English
502
378
5.6K
477.8K
Rod Johnson retweetledi
Bruno Souza
Bruno Souza@brjavaman·
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.
Bruno Souza tweet media
English
2
2
7
1.1K
Rod Johnson
Rod Johnson@springrod·
@shanselman Infuriating, isn’t it. What human actually wrote like that??
English
1
0
2
814
Scott Hanselman 🌮
Scott Hanselman 🌮@shanselman·
"just dropped" "killed every ____ with this one simple" "absolute game changer" "here's the real unlock" "this 20 line md skill changes everything"
English
50
20
414
46.9K
Daniel Dent
Daniel Dent@oilersbluesky·
@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
English
1
0
1
322
Makakmayum
Makakmayum@makakmayum_sid·
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
English
4
9
134
10.1K