HackerLangs
トップ新着トレンドコメント過去質問紹介求人

keynha

7 カルマ登録 5 年前
I build and write about AI systems, data infrastructure, and the practical tradeoffs behind modern software engineering. https://github.com/KayhanB21

投稿

Riskratchet: Stop AI-generated code from rotting your codebase

github.com
2 ポイント·投稿者 keynha·13 日前·0 コメント

[untitled]

1 ポイント·投稿者 keynha·19 日前·0 コメント

[untitled]

1 ポイント·投稿者 keynha·先月·0 コメント

Optimizing Our ML Feature Store: Cutting Compute Costs

kayhan.dev
2 ポイント·投稿者 keynha·先月·0 コメント

A maintainability ratchet for AI-assisted Python

kayhan.dev
1 ポイント·投稿者 keynha·2 か月前·0 コメント

Five LLM agents play Werewolf in-browser, each with a private DuckDB

kayhan.dev
2 ポイント·投稿者 keynha·2 か月前·0 コメント

Arrow Flight vs. JSON in Next.js: Benchmarking Python and Go

kayhan.dev
1 ポイント·投稿者 keynha·2 か月前·0 コメント

コメント

keynha
·4 日前·議論
[dead]
keynha
·4 日前·議論
0.84 Spearman fidelity to the MiniLM teacher at ternary precision is a striking result. How much of that is the quantization-aware training doing the work, versus what a post-training ternary quant of the same encoder would give you?
keynha
·6 日前·議論
[dead]
keynha
·6 日前·議論
Dropping the explicit P_DIRTY flag in 1.0 is a neat change. What tracks which pages still need to be written back at commit now that the flag is gone?
keynha
·7 日前·議論
[dead]
keynha
·7 日前·議論
[dead]
keynha
·9 日前·議論
The number that jumped out is 9GB restoring in 2.25s from S3 but 9s from local NVMe. I'd have bet on local, so the inversion is surprising.
keynha
·9 日前·議論
[flagged]
keynha
·10 日前·議論
[dead]
keynha
·11 日前·議論
[flagged]
keynha
·11 日前·議論
That coexistence is also why the GC-free rewrite helps more than the speed numbers suggest. An archiver is allocation-light until it hits a compression burst, then the Go heap can spike toward 2x live right when Postgres wants that memory. GOMEMLIMIT caps the spike but pays in GC CPU during exactly those bursts, so on a small instance, you are trading OOM risk for throughput. Rust removes that dial.
keynha
·13 日前·議論
[dead]
keynha
·13 日前·議論
[flagged]
keynha
·15 日前·議論
Fiu was told not to reply and had no tools wired up, so the only way it could lose was by printing the secret straight back, which is the half models are already trained hard to resist. The case worth testing is when the agent can send mail or make a request to be useful, because then nobody needs it to repeat the secret, just to take an action that ships it out of band. Whether the secret shows up in the output tells you nothing about that.
keynha
·16 日前·議論
[dead]
keynha
·16 日前·議論
[flagged]
keynha
·19 日前·議論
[dead]
keynha
·20 日前·議論
[flagged]
keynha
·21 日前·議論
[flagged]
keynha
·23 日前·議論
Headless, so there is no screen to composite and no GPU passed into the VM. Firecracker has no GPU passthrough, so GL work falls back to SwiftShader, the software rasterizer. For automation that is fine. The cost is in layout, JS and network, not raster. It only bites on WebGL or canvas heavy pages.