kouteiheika

11 ms·

1.
by kouteiheika 4d ago
It's almost certainly A/B test. Essentially everyone does it. You can even sometimes see when a list of videos on YT first loads and a given video has one title, and it suddenly switches to another without you reloading the page.
2.
by kouteiheika 5d ago
> They're cool with open weight AIs being released. As long as those AIs only ever say good things about CCP, and don't mention certain concentration camps or brutally suppressed protests. I asked recently released Qwen3.8-Flas
3.
by kouteiheika 5d ago
It's not a VM; it's containerized with a FUSE-based custom overlay, and the agent never touches a real mount (with two exceptions: passthrough read-only mounts for things like /bin, and ephemeral tmpfs mount at /tmp).
4.
by kouteiheika 5d ago
> What I've found difficult with harness design is deciding which features are actually going to be useful, and which ones are cool-sounding ideas that get people talking, but nobody actually uses in practice. It should be easy to t
5.
by kouteiheika 5d ago
> And every time I wonder where the people who create these tests are looking when they're deciding which harnesses to test? Well, everyone and their dog has a custom harness now (including myself!), and more often than not they&#x2
6.
by kouteiheika 6d ago
Yep. Just like a kitchen knife will make no attempt to prevent me from stabbing anyone with it. Here's a dirty secret though -- you don't actually need an abliterated/uncensored version of the model to get it to do this. I ca
7.
by kouteiheika 6d ago
> posts on American models are steered towards controversy and anti-AI sentiment, posts on Chinese models are full of blatant flattery So why, for example, are posts on the Inkling[1] release (an American model) thread mostly positive? I
8.
by kouteiheika 6d ago
Excuse me for not being interested in over 100 pages of how well the model can refuse and block my requests, especially considering how fun it is to waste my time trying to get around those restrictions when they inevitably trigger because
9.
by kouteiheika 6d ago
It's so refreshing to see DeepSeek's tech report[1] full of juicy details; meanwhile, something like Fable's system card[2] is like 70% "safety", 10% "model welfare" to make sure little Claude isn't d
10.
by kouteiheika 7d ago
> Did anyone else notice that all the use cases they show here are "use ChatGPT Images to imagine all the things you'd like to have, but don't"? What else could they highlight? The other major use case for these model
11.
by kouteiheika 8d ago
Note that these quants are not quantized uniformly, so 4-bit isn't actually a "true" 4-bit here, so these observations won't necessarily hold up to other quants which might be done differently.
12.
by kouteiheika 12d ago
> Specifically, all it took to boost Qwen3.8-27B to get 10% more points on SWEbench Pro and Terminal Bench 2.0 with a proxy that has just these basics Do you have a link/paper for this you could share?
13.
by kouteiheika 12d ago
> because their output is non-deterministic by design. It isn't. At least not by design, even though in practice it often can be. If you do greedy decoding (or use a preset seed) and deterministically compute everything (e.g. only u
14.
by kouteiheika 12d ago
> Models like ornith:9b, mistral:7b or cogito:14b can get the job done sometimes, but they are not fast and reliable enough for general use, specially if you have only 4GB of VRAM. Have you considered/tried using a model that's
15.
by kouteiheika 13d ago
FWIW I had the same reaction to the popups. Immediately closed the tab.
16.
by kouteiheika 16d ago
> This is a real problem, and it’s not just in markdown files and docs. Claude loves to write things we’ve “discovered” in comments and then later in treats the comments as gospel truth. There's a simple fix for this: do not let it
17.
by kouteiheika 16d ago
> In my company we use graphite and stacked PRs so it is highly encouraged to keep one commit per PR, so I am constantly ammending my commits. So this makes it even simpler for you. Then you don't have to care at all about keeping y
18.
by kouteiheika 16d ago
> The problem with sandboxing is that the regular dev env (massive IDE:s, cloned megarepos, installed dependencies and so on) just won't sandbox very easily. It's not that hard, actually. You don't need VMs. You usually do
19.
by kouteiheika 16d ago
> yeah, but if you don't want to lose your existing context sometimes you have to Sorry, I'm not sure I follow. What do you mean by "lose your existing context"? Can't you just... commit in turns? It's not l
20.
by kouteiheika 16d ago
> I made changes to my dependency lists in the same code where Claude ran npm update. ...but was it in the same commit? Two "update lockfile" commits, one yours and one Claude's should have made this obvious, no? Here&#x27
21.
by kouteiheika 16d ago
> No one is going around checking every single line change in auto-generated files. There's a simple fix for your particular case: commit your lock fine (which you should do) and always review the diff (which you should also do). (:
22.
by kouteiheika 17d ago
Did you actually try to convince them? Again, this requirement is incredibly silly. Here, look at this (it's a link to AA; I shortened it since the link's huge): https://tinyurl.com/2dhzdrt6 Right now, the best US
23.
by kouteiheika 17d ago
> Gated in that I cannot use non-US models. This is incredibly silly. First I would try to convince whoever has decreed this to reconsider. The only SOTA open-weight models are non-US, and rather than being afraid of potential Chinese ba
24.
by kouteiheika 18d ago
> if you want to always stay on the bleeding edge (and not use their model-specific images they publish before it lands in a release), then some amount of patching might be needed especially for new models. Well, except this isn't e
25.
by kouteiheika 18d ago
Prompt was completely unrelated and was nothing special. Just a batch job to translate a bunch of benign sentences from one language to another. I'm afraid credit here fully goes to vLLM, and whatever bug triggered this.
26.
by kouteiheika 18d ago
> What's you opnion vs. SGLang in this regard? No opinion yet, but I'm planning to temporarily switch and see how it goes. I really hope the grass is greener there, but I'm keeping my expectations in check for now.
27.
by kouteiheika 18d ago
I love vLLM, but damn if it isn't frustratingly buggy. I was recently running DeepSeek-V4-Flash on a B300. On v0.26 it was totally broken, and I had to add three out-of-tree patches to fix it. I updated to v0.27 -- no patches necessary
28.
by kouteiheika 18d ago
> Engineers complained that their agent made unhelpful comments and produced low-quality output. Do you mean they found Claude's output, full of smoking-guns and honest caveats which are all load-bearing and genuinely bite -- they f
29.
by kouteiheika 1mo ago
Ah, okay. Sorry, fair enough!
30.
by kouteiheika 1mo ago
> but they omit the tool definitions. Those are much more interesting if you want to understand what Claude can actually do for you. You can reconstruct them through prompting Claude directly but that's extra friction and risks refu

More ›