HackerLangs
TopNewTrendsCommentsPastAskShowJobs

keynha

7 karmajoined 5 ปีที่แล้ว
I build and write about AI systems, data infrastructure, and the practical tradeoffs behind modern software engineering. https://github.com/KayhanB21

Submissions

Riskratchet: Stop AI-generated code from rotting your codebase

github.com
2 points·by keynha·13 วันที่ผ่านมา·0 comments

[untitled]

1 points·by keynha·20 วันที่ผ่านมา·0 comments

[untitled]

1 points·by keynha·เดือนที่แล้ว·0 comments

Optimizing Our ML Feature Store: Cutting Compute Costs

kayhan.dev
2 points·by keynha·เดือนที่แล้ว·0 comments

A maintainability ratchet for AI-assisted Python

kayhan.dev
1 points·by keynha·2 เดือนที่ผ่านมา·0 comments

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

kayhan.dev
2 points·by keynha·2 เดือนที่ผ่านมา·0 comments

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

kayhan.dev
1 points·by keynha·2 เดือนที่ผ่านมา·0 comments

comments

keynha
·4 วันที่ผ่านมา·discuss
[dead]
keynha
·4 วันที่ผ่านมา·discuss
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 วันที่ผ่านมา·discuss
[dead]
keynha
·6 วันที่ผ่านมา·discuss
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 วันที่ผ่านมา·discuss
[dead]
keynha
·7 วันที่ผ่านมา·discuss
[dead]
keynha
·9 วันที่ผ่านมา·discuss
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 วันที่ผ่านมา·discuss
[flagged]
keynha
·10 วันที่ผ่านมา·discuss
[dead]
keynha
·11 วันที่ผ่านมา·discuss
[flagged]
keynha
·11 วันที่ผ่านมา·discuss
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 วันที่ผ่านมา·discuss
[dead]
keynha
·13 วันที่ผ่านมา·discuss
[flagged]
keynha
·15 วันที่ผ่านมา·discuss
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 วันที่ผ่านมา·discuss
[dead]
keynha
·16 วันที่ผ่านมา·discuss
[flagged]
keynha
·19 วันที่ผ่านมา·discuss
[dead]
keynha
·20 วันที่ผ่านมา·discuss
[flagged]
keynha
·21 วันที่ผ่านมา·discuss
[flagged]
keynha
·23 วันที่ผ่านมา·discuss
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.