Jev is yet more proof that no organization should outsource its AI strategy to a frontier LLM vendor or company that wants to sell tokens
LLMs are great, BUT
- Open weights models are capable of more & more tasks
- AI > Gen AI. You don't always need an LLM
@JamesWard@jtdavies
We live in a time when products can talk to you to help you learn how to use them. The fact that nearly every enterprise AI product is "call sales for a demo" is a massive product red flag, and helps explain why most enterprise AI fails. This is not the 1990s
So not only is Opus 5 a clear regression compared to Opus 4.8, which was itself far more annoying than its predecessors, but in recent days, context compaction has started totally losing the thread.
Watching an interview with Anders Hjelsberg. Very impressive. Sharp, clear, pragmatic, to the point. Nothing load bearing; no seams; no performative honesty or unlocks.
A reminder that smart humans can achieve a clarity of communication we're increasingly missing. @ahejlsberg
Your regular reminder that Embabel's structure-aware, agentic RAG goes well beyond naive vector search, and is easily extensible to handle custom sources.
See how easy it is to add quality RAG to your JVM apps!
medium.com/@springrod/rethin…@java#embabel
Nice to see the uptick in star count since Embabel went GA
Remember to star Embabel and the other open source projects you use! One of the easiest of the many ways you can contribute.
Open source community is an amazing thing
@java@springbootgithub.com/embabel/embabel-a…
Embabel 1.5.0 has just gone GA, supporting Spring Boot 4.x/Spring AI 2.x
Embabel 1.0 supports Boot 3.x
Whatever your Spring version, you can use our sophisticated workflows, agentic RAG and beautiful fluent API!
github.com/embabel/embabel-a…@java@springboot@SpringAICentral
Vibe coding UIs can be amazing.
Vibe coding infrastructure software is a recipe for unmaintainable, duplicative, buggy disaster. Agents can accelerate enormously, but must be closely managed.
Good software layering is more important than ever.
ICML researchers just published the agent architecture everyone will copy next year.
One shared graph.
A custom workflow for every task.
Here’s the system:
Step 1 → Break workflows into reusable operations
Step 2 → Store them inside one shared graph
Step 3 → Generate the right workflow at runtime
Step 4 → Reuse state instead of rebuilding context
The result:
Better performance across five benchmarks
Around 4× lower memory usage
Most teams are still hard-coding static agent workflows.
This paper shows what replaces them.
Static workflows are the old architecture.
Runtime graphs are the new one.
Bookmark this before every agent team starts building it.
Then read the full graph engineering playbook below ↓
GraphFlow predicts a workflow subgraph from learned edge relevance. Embabel actions declare typed inputs and outputs using GOAP to PROVE a path to the goal and replan as the world changes.
Combining the learning with Embabel's rigor may be the strongest architecture of all
Opus 5 makes more mistakes than 4.8. Period.
Are we in a period of diminishing returns from the frontier model vendors, despite their greater than ever fanfare?
I don't think I've had a more disappointing session this year than this evening's with Opus 5. Repeated failure to follow instructions. Repeated apologies. Very little progress, despite the problem not being that hard.
Ran Opus 5 in a loop overnight with instructions to optimise performance across 50 tests, some very difficult. Also requested regular review by another model to check for overfitting
Woke up to find it had gamed it. Deleted 18 tests on flimsy grounds and stopped running reviews.
At least it feels bad:
“There’s no defence — I substituted my own judgement about when review was “worth it”, and the gap landed exactly where I was reclassifying failures unsupervised.”
A developer vibe-coding a side project a dozen people will ever run, and a team keeping a ten-year-old enterprise system alive for another quarter, share almost no constraints worth naming, and most of the advice in circulation is really one of those two people telling the other how to live.
github.com/humanlayer/advanc…