It's derived from github.com/mukel/llama3... .
jinfer is a modern, serious attempt to bring AI to the JVM.
It supports all the latest open models Gemma 4, Qwen 3.5+, LFM 2.5, gpt-oss, Nemotron, Kokoro, Parakeet... competitive with llama.cpp on CPUs.
Already integrates with LangChain4j and Spring AI.
A friendly reminder that #Java#HelloWorld looks like this since Java 24:
void main() {
println("Hello World");
}
No, it is not "public static void main..." anymore. 🫶
Saw this talk in Antwerp and loved the one-jar principle. Inspired by it, built some UIs to test Quixotic features in a Java/Spring Boot app: github.com/samie/quixot...
Hey folks in BERLIN! I'll be in the area from 8-26 November and would love to give a talk about Event Sourcing to your group, meetup, or company (no charge!). Other than 15-19 Nov (I'll be at Agile Testing Days), let me know and see my travel details at: jittertravel.com
The presenter asked for a headset mic. Two weeks ago. In an email chain that got buried.
Now I'm interviewing AV company owners about where show info gets lost between client call and show day.
15-min audit call: I share what I've learned, you shape the tool. DM me.
Java SDK + Spring AI integrations for #TypeSafe AI's #Jev.
Not a chat model! Send it a state and typed questions, get numbers back with a confidence, in ~300 ms.
Judge, self-refine + guardrail advisors, RAG triage, tool selection.
Blog: spring.io/blog/2026/09...@spring-ai.bsky.social
Java SDK + Spring AI integrations for #TypeSafe AI's #Jev.
Not a chat model! Send it a state and typed questions, get numbers back with a confidence, in ~300 ms.
Judge, self-refine + guardrail advisors, RAG triage, tool selection.
Blog: spring.io/blog/2026/09...@spring-ai.bsky.social
Hey Spring fam 🍃
My early access book "Testing Spring Boot Applications" with @manning.com is Deal of The Day.
Get 45% off the book, and a selection of other testing books, here: hubs.la/Q03-d27Y0
First 4 chapters online, the 5th is coming out soon, and putting finishing touches to chapter 6.
Checking dependency upgrades is now a tool-tip away
#DependencyAssistant 1.0 is GA now
plugins.jetbrains.com/plugin/30958...#Maven#Gradle#NPM#GitHubActions
Curious about event sourcing but not sure where to start? 💭
Build a feature from the events up in this hands-on workshop with @ted.dev at #dev2next and see how event sourcing works in practice.
🔗 www.dev2next.com/schedule
🎟️ Get tickets: dev2next.com
📅 October 12-15
#EventSourcing#Java
Reminder that tonight I'm speaking in Hamburg (at the Microservices Meetup) about #EventSourcing! I know it's short-notice, but if you're around, come on by and let me share with you my passion on the topic! www.meetup.com/microservic...
New multi-skill AI workshop now available.
100% free and open; no email required.
1. Determine your pricing strategy
2. Figure out why they’re compelled to buy
3. What to build next to justify raising prices
Curious about event sourcing but not sure where to start? 💭
Build a feature from the events up in this hands-on workshop with @ted.dev at #dev2next and see how event sourcing works in practice.
🔗 www.dev2next.com/schedule
🎟️ Get tickets: dev2next.com
📅 October 12-15
#EventSourcing#Java
Our extension for Claude Code can tell your agent what seems to be wrong with your project from a Spring perspective by deliverung diagnostics information directly to the agent - pretty nice to safe tokens and to enhance the agent with more Spring smartness 😎🥳
To carry 50,000 people per hour in each direction, a city needs a 175m wide road for cars.
Even if those cars are electric.
And then there’s all the parking.
OR a city can move A LOT MORE people in a lot less space, with A LOT LESS public money, emissions, pollution, noise etc.
Choices.
Simple.
We all know a general session and a breakout. What do you call every other meeting/session happening as part of the conference that is bigger than a breakout, but is not the general session?
A. Concurrent Session
B. Ancillary Meeting
C. Something else
Curious about event sourcing but not sure where to start? 💭
Build a feature from the events up in this hands-on workshop with @ted.dev at #dev2next and see how event sourcing works in practice.
🔗 www.dev2next.com/schedule
🎟️ Get tickets: dev2next.com
📅 October 12-15
#EventSourcing#Java
Most production schedules treat the "Technical Needs" column like a dumping ground.
When a project manager dumps an entire warehouse pull sheet into a single spreadsheet cell, the onsite crew stops reading it. Chaos follows at 7:00 AM.
Flag only what's unusual about this specific room, session, or client:
- Slide notes on confidence monitor
- Presenter prefers a HH mic
That flag is what saves the show day.
When you run complex, multi-room corporate events, your show book dictates whether your team walks in calm or scrambling.
Most production schedules treat the "Technical Needs" column like a dumping ground.
When a project manager dumps an entire warehouse pull sheet into a single spreadsheet cell, the onsite crew stops reading it. Chaos follows at 7:00 AM.
A production schedule isn't an inventory list - it's a coordination tool. Its job is to preserve high-level situational awareness, not document every cable in the truck.
So trim that column to the outliers.
> "The scary part is that I might lose some of this information."
A multi-day, multi-room conference gets scheduled months out - across dozens of meetings and emails.
Somewhere in client meeting #9 of 14, the keynote speaker mentions needing a headworn mic and wanting to walk out to "Happy.
Noticed they weren't staged. Called the shop for a rush delivery and tethered to his phone to pull the track.
Chris Shelton has been producing events like this for years. He puts it simply:
"Companies that hang with the details are remembered.
> "The scary part is that I might lose some of this information."
A multi-day, multi-room conference gets scheduled months out - across dozens of meetings and emails.
Somewhere in client meeting #9 of 14, the keynote speaker mentions needing a headworn mic and wanting to walk out to "Happy.
"
The mic made it onto the pull sheet. Then got swapped for a lavalier during packing. No one downloaded the music.
Six months later, the keynote speaker arrives at the event.
She has everything she asked for.
How?
The A1 reviewed the production schedule that morning. Noticed the requirements.
Do you have a Launchpad?
My friend Dave is looking for beta testers for his new app that turns your Launchpad into an audio meter. Contact him through the website ->
Most developers expect a test to fail. Ted M. Young argues that the real value comes from predicting exactly how it will fail.
When the result doesn’t match your expectation, you’ve uncovered a misunderstanding before it becomes a bug.
Six months before show day, your client mentioned her CEO always walks on to "Girl on Fire."
It came up once. Near the end of a 40-minute call.
You put it in the production schedule.
On show day: right song, right moment. She didn't even have to remind you. Nailed it.
A show book is not just a coordination tool for crew - it's a promise-keeping system for clients.
Walk-on music. Presenter mic preferences. "Our speaker hates lavalieres." The specific thing mentioned once, months out, that would otherwise vanish into email threads and half-remembered notes.
A script with cues might be more appropriate, but if there's only one cue, just note it in the show book.
What's the smallest client detail you've ever caught in a schedule that made a real difference on show day?
Are you in or near Leipzig on Tuesday evening? Don't miss my talk at the Leipzig Software Crafter Community!
(See where else in Europe I'll be: ted.dev/where/)
Details and registration at www.meetup.com/le-software...
Curious about event sourcing but not sure where to start? 💭
Build a feature from the events up in this hands-on workshop with @ted.dev at #dev2next and see how event sourcing works in practice.
🔗 www.dev2next.com/schedule
🎟️ Get tickets: dev2next.com
📅 October 12-15
#EventSourcing#Java
The production schedule isn't a pull sheet.
That lives in your Lassos, Flexes, and Current RMSes.
But, a production schedule can help highlight outliers and serve as a quick reference.
As a sound tech, I'd prefer to see "8 lavs, 2 handhelds" than need to find the pullsheet and count up the inventory.
How are you handling this in your show book?
A production schedule that says "AV Tech" isn't a schedule for anyone.
The moment you swap job titles for actual names - not "Sound Tech," but "Alex" - something shifts.
The schedule becomes personal. Filter by name and a 50-row show collapses to the 11 rows that are actually Marcus's today.
What if you sorted your production schedule by Day → Room → Time instead of Day → Time?
You'd get something interesting.
Instead of a show book where Room 1 and Room 3 and the Ballroom are all interleaved by clock... each room gets its own block.
The manager still sees everything.