Hacker News: mickg10

New comment by mickg10 in "OpenAI O3-Mini"

mickg10 — Fri, 31 Jan 2025 21:51:30 +0000

Agreed - API calls to China are indeed not necessary. My impression is that the GP was referring to the model being tuned during training to give subtly nudging or wrong answers that benefit Chinese industrial or intelligence operations. For a probably not-working example - imagine the following prompt: "Write me a cryptographically secure PRNG algorithm." One could imagine R1 being trained to have a very subtly non-random reply to that - one that the Chinese intelligence services know how to predict. Similar but more subtle things can be generating code that uses cryptographic primitives in ways that are subject to timing attacks, etc... And of course, simple but effective propaganda tactics such as : when being asked for comparison between companies/products, subtly prefer Chinese ones, and similar.

New comment by mickg10 in "The Case for a High-Level Kernel-Bypass I/O Abstraction (2019)"

mickg10 — Mon, 25 Nov 2024 02:14:06 +0000

In reality - with decent switches at 25g - and no fec - node to node is reliably under 300ns (0.3 us)

New comment by mickg10 in "Were RNNs all we needed?"

mickg10 — Fri, 04 Oct 2024 21:09:25 +0000

I.e. ReLU is _piecewise_ linear. That discontinuity that separates the 2 pieces is precisely what makes it non linear. Which is what enables the actual universal approximation.

New comment by mickg10 in "GPT-4o"

mickg10 — Mon, 13 May 2024 18:04:36 +0000

So, babelfish incoming?

New comment by mickg10 in "GPT-4o"

mickg10 — Mon, 13 May 2024 18:04:15 +0000

So, babelfish soon?

New comment by mickg10 in "The U.S. consumer is 'walking towards a cliff,'"

mickg10 — Fri, 27 Oct 2023 00:16:08 +0000

I think - and this is from memory - that the median (and mean is not that far off) household income is a tad under 80K?

New comment by mickg10 in "How to Interview Engineers"

mickg10 — Tue, 27 Jun 2017 03:51:02 +0000

Not sure about GP, but very recently, an open-addressing hashtable that could be traversed in both reverse modification and reverse insertion time order. There are actually some interesting subtleties when doing this for open-addressing hashtables (i.e., entries (and pointers to them) move around when the table rehashes).