Big congrats to my friend! 🎉
He just launched a family #cardgame called The Elements ♠️🔥🌊
I was lucky to be a tester, and now the crowdfunding is LIVE on @gamefound 🚀 Check it out, like it & support if you vibe with it ❤️
👉 https://t.co/4BBk5kf7Eq
💡 Just in case — if you're using #Embabel with @Gradle, don't forget to add:
repositories {
maven {
url 'https://t.co/EBZqjZfe4y'
}
}
...or enjoy hours of debugging fun™️ 🤡
#ai#agent#embabel#gradle
🍃 Null Safety in Java with JSpecify and NullAway by @sdeleuze @ Spring I/O 2025
▶️ Video: https://t.co/PLi4kmNwIg
🔗 Slides: https://t.co/hHgwBjdZF0 #springio25
If you’re using @Google Cloud #TextToSpeech feature, you might be surprised to find that some voices have been removed 😲
Just in case, here is a helpful doc
👉 https://t.co/2fhv174JDc
First blog post in a year — what a streak 😅
I built a simple way to run tests for your @OpenFGA models — including a @GitHub Actions you can plug straight into your workflow.
Check it out 👉 https://t.co/asbDEgTGnv
#OpenFGA#Authorization#GitHub
@therealdanvega - Or maybe you’re just cruising around AI and JTE, and those topics aren’t interesting anymore🤔
Some quick stats: out of the last 15 articles, there were:
- 8 about AI
- 5 about JTE
- 2 about Java
@kehrlann@piotrprz@intellijidea I were sitting in that chair when the lockdown started - since there weren’t any available in warehouses 🤦♂️
I feel it’s as necessary as an @intellijidea license 😅
💎 #JUnit Diamonds 💎
When you are using @ParameterizedTest and want to pass null, use the @NullSource annotation, which provides a single null argument to the method.
https://t.co/bPJ8UGyHM7
I have done a lot of explorations while implementing OTel in our applications.
I considered 3 options:
1⃣OTel JavaAgent
2⃣Micrometer
3⃣OTel Spring Starter
My thoughts:
1⃣Currently, this is the best option for me.
✅I really like the almost out-of-the-box instrumentation for Spring MVC, RestClient, Spring Data, and Spring AMQP (RabbitMQ).
✅Static means of setting traces/spans/context customizers like Span.current().setAttribute() are very convenient (I don't need to inject Tracer).
✅Zero configuration, which doesn't interfere with business code.
❌Missing very convenient SpEL expression support.
2⃣I don't like the amount of manual work and interference with business logic due-to-configuration and injecting traces.
✅Really nice SpEL support.
❌Missing out-of-the-box support for Spring AMQP and Data Repositories.
❌Missing JPA instrumentation.
❌Very inconsistent properties. Figuring out which property to use is a nightmare. Some start with management.opentelemetry.*, others with management.otlp.*, and yet others with management.tracing.*
3⃣This is unusable if you want to follow the latest @springboot versions.
Those were my observations so far. Next week, now I will explore metrics 😉