fwystup

Can confirm - their footer links a "How We Write" page: content is "AI-generated, software-refined, and human-curated."

Fun fact: I double-checked with my AI, which concluded: "The original HN post is, by the way, considerably more worth reading than the rehash."

My opinions about the study:

- Don't state the obvious: I wouldn't hand a senior human dev a copy of "Clean Code" before every ticket and expect them to work faster.

- File vs. Prompt is a false dichotomy: The paper treats "Context Files" as a separate entity, but technically, an AGENTS.md is just a system prompt injection. The mechanism is identical. The study isn't proving that "files are bad," it's proving that "context stuffing" is bad. Whether I paste the rules manually or load them via a file, the transformer sees the same tokens.

- Latent vs. Inferable Knowledge: This is the key missing variable. If I remove context files, my agents fail at tasks requiring specific process knowledge - like enforcing strict TDD or using internal wrapper APIs that aren't obvious from public docs. The agent can't "guess" our security protocols or architectural constraints. That's not a performance drag; it's a requirement. The paper seems to conflate "adding noise" with "adding constraints."

Really interesting Project, thanks for sharing. Reminded me a bit of my time coding assembly on the C64 (yeah, I'm old). For 3D (wire-frame) we also needed to find creative ways around hardware limitations, especially the lack of a multiply instruction.

Posted almost at the same time about Kata. I'm trying to use Kata as replacement for the standard docker runtime (since I already have a tool based on docker).

The idea is to simply use the runtime flag (after kata install):

docker run -d --runtime=kata -p 8080:8080 codercom/code-server:latest

Hope this works, with this I could keep my existing docker setup.

I'm currently building a Docker dev environment for VSCode (github.com/dg1001/xaresaicoder) usable in a browser and hit the same issue. Without docker-in-docker it works well - I even was able to add transparent proxy in the Docker network to restrict outbound traffic and log all LLM calls (pretty nice in order to document your project). For docker-in-docker development and better security isolation, I'm considering Kata Containers instead of Vagrant. Which gives me real VM-level isolation with minimum perf overhead, while still be able to use my docker stuff. Still on my TODO list though. Has anyone actually run Kata with vs code server? Curious about real-world quirks - I've read that storage snapshot performance can be rough.

Does anybody also see this with claude code and haiku 4.5 (tried to set the env var, no change): "API Error: Claude's response exceeded the 8192 output token maximum. To configure this behavior, set the CLAUDE_CODE_MAX_OUTPUT_TOKENS environment variable."?

Glad to hear it. Your NLTK approach sounds interesting — would love to hear more about it. BTW, I’m planning to improve my project’s documentation. Funny enough, under “consideration” it flagged itself: "Documentation quality is not explicitly high. The effectiveness of the LLM’s scoring criteria is subjective and not deeply explained." Sadly, that’s true.

Got it, thanks for clarifying. Makes sense that participation matters more than raw karma. I’ll keep that in mind and try to contribute more broadly, posting less about my own projects.

You're right — I totally missed that. Fixed it, please reload.

Thanks for the feedback — definitely not meant as spam. It’s open source, not a commercial blog. Just wanted to surface some fresh ideas that might otherwise get missed. Really appreciate the tip!