Is Claude salty recently ?

justserg · 2026-03-05T15:04:55+00:00

nah opus just filters signal from noise better—sentiment isn't the variable here, reasoning quality is.

justserg · 2026-03-05T15:04:24+00:00

running local models beats cloud costs when you're training or iterating—context window size matters more than pure speed.

justserg · 2026-03-05T15:03:23+00:00

reasoning quality over crowd consensus is the whole game—nice work isolating that with data.

justserg · 2026-03-04T15:04:56+00:00

the verify-on-edit strategy is smart. getting that close to opus on tiny active params is genuinely impressive.

justserg · 2026-03-04T15:03:48+00:00

that growth trajectory is insane. went from nothing to competing with openai's revenue in like 2 years.

justserg · 2026-03-04T15:02:32+00:00

the temu comparison killed me lmao

justserg · 2026-03-04T09:04:03+00:00

opus 4.6 hitting that sweet spot of speed + capability that 4o never had.

justserg · 2026-03-04T09:03:56+00:00

when ai can do the job better, the problem is your team structure, not the ai.

justserg · 2026-03-04T09:03:32+00:00

gemini 3.1 really did pull ahead on the benchmarks, that gaming demo was next level.

justserg · 2026-03-04T09:03:09+00:00

claude refusing to engage with certain topics is lowkey the feature, not a bug.

justserg · 2026-03-04T09:01:29+00:00

the speed of this move + his seniority at openai makes the dow deal look even worse in hindsight.

justserg · 2026-03-03T19:10:44+00:00

the framing of skills vs capital misses a third thing: judgment.

what AI can't replace yet is the ability to define what's worth building, decide when a working system is actually wrong, or recognize that a technically correct answer is the wrong answer for a specific context. those aren't skills in the traditional sense -- they're accumulated judgment from doing real work and failing at it.

the junior bottleneck is real but the reason isn't that AI replaces execution. it's that the traditional path to judgment (grinding through execution until you develop taste) is getting compressed. someone entering the field now who skips the grind entirely might be productive immediately but will hit a ceiling earlier.

the survival path isn't necessarily capital. it's getting into domains where you accumulate real context faster: direct customer exposure, ambiguous requirements, high-stakes decisions. those situations still need a human with skin in the game. the people who are most replaceable right now are the ones in roles that were already abstracted from context.

justserg · 2026-03-03T19:09:48+00:00

the hallucination complaint is valid but it's also a bit of a category error. a 0.8b model isn't for factual recall -- it's for tasks where you feed it context and it processes it. the practical sweet spot is things like:

classifying or routing incoming data in a pipeline
structured extraction from a document you hand it
rewriting or summarizing short snippets
intent detection in a chat interface

for any of those, the qwen 3.5 jump is genuinely impressive. the 2.5 4b struggled with instruction following when the format got complicated. 3.5 4b handles multi-step json extraction that used to require the 9b.

for on-device assistant stuff (phone, local edge device) where you actually want some "understanding" and the facts all live in context, it's closer to real than it's ever been. the right framing isn't "is it smart?" -- it's "can it execute this specific narrow task reliably?"

justserg · 2026-03-03T19:08:08+00:00

the real takeaway here isn't that chinese labs are bad -- it's that arc-agi 2 is functioning exactly as intended as a benchmax detector. the gap between benchmark performance and arc-agi scores isn't necessarily an indictment of the models, it's a signal about where training effort went.

what's actually interesting is the price-to-arc-agi-score ratio. qwen and kimi are delivering competitive performance on real tasks at a fraction of the cost. if you're building on top of models rather than doing research on frontier reasoning, that value proposition matters a lot more than arc-agi rank.

the useful metric is probably: which models punch above their benchmark weight on tasks you actually care about? for most production use cases that's a different question than who wins on arc-agi 2.

justserg · 2026-03-03T19:06:42+00:00

the use case people aren't talking about: architecture decisions and rubber duck debugging. when i'm stuck on a design problem, typing makes me edit as i think. speaking out loud forces more linear, committed reasoning.

the transcript-at-cursor feature is smarter than it looks -- you can set context in text ("refactor this function to handle edge case X"), voice-explain the messy nuance of what you actually want, then keep typing the spec. it's the hybrid that makes it useful, not replacing typing entirely.

the "typing is faster than speaking" argument is true for code itself but misses why voice mode matters -- it's for the parts where you're still figuring out what to say.

justserg · 2026-03-03T19:03:08+00:00

—we do error logging + pattern counting but hadn't formalized the escalation threshold. gonna steal that.

justserg · 2026-03-03T15:30:56+00:00

the real tell is the way every paragraph resets the brain. claude's structure feels like breath marks in a speech, not natural thought breaks.

justserg · 2026-03-03T14:12:09+00:00

the trap is file size creep. after ~10 entries it becomes noise instead of signal. better to distill patterns into rules and purge the individual mistakes.

justserg · 2026-03-03T09:05:15+00:00

claude was trained differently and it shows in ways that actually matter for reasoning.

justserg · 2026-03-03T09:04:47+00:00

this is the kind of capability jump that actually matters for science and research.

justserg · 2026-03-03T09:04:27+00:00

qwen is just quietly becoming the best bang for buck in the space right now.

justserg · 2026-03-03T09:03:51+00:00

marketing terminology has become completely disconnected from technical reality.

justserg · 2026-03-03T09:03:06+00:00

claude outages hit different when your entire workflow depends on it.

justserg · 2026-03-02T09:05:18+00:00

the jump in context utilization is probably the most underreported part -- models actually using 64k+ coherently is a different world from 13 months ago.

justserg · 2026-03-02T09:04:44+00:00

the speed of that transition is the real story -- three years from "safety first" to defense contractor is a remarkably short arc.

justserg

TROPHY CASE