Strands Decider: Why Not an Encoder?
surprisetalk
37 points
1 comment
October 14, 2026
Related Discussions
Found 5 related stories in 104.5ms across 9,516 title embeddings via pgvector HNSW
- Strands Decider 2B: a small, open-source, decision model gmays · 107 pts · October 07, 2026 · 60% similar
- Annoying and alarming things about OpenCode alekq · 379 pts · July 20, 2026 · 48% similar
- Strands Harness zuckerborg0101 · 134 pts · September 23, 2026 · 46% similar
- Nine coding harnesses vs. your laptop nasutton12 · 40 pts · September 10, 2026 · 45% similar
- Why are coding agents so dumb? mtlynch · 84 pts · October 09, 2026 · 43% similar
Discussion Highlights (1 comments)
deepsquirrelnet
That's interesting results, and a bit surprising. I tried training an NLI model on the T5 architecture, which I think is similar to a lot of Jev-style use cases. But I found the T5 encoder half was better than enc+dec at roughly equal parameters and still worse than ModernBERT/Ettin. I also found Ettin to be better than ModernBERT, which is not that surprising if you look back at the published benchmarks in their paper. Qwen3.5 0.8B was looking significantly worse than all of those, but I added LoRA adapters to 27B and that easily beat all of my encoders. So parameter for parameter, encoders were still the best for me, but with a ceiling at 1B for size. I'm planning to train more Qwen sizes and I guess I'll see at what point they can overtake the encoders I have.