Viewing profile — jhgg

We just track power utilization.

Cool article :)

Yes, agreed, hence rarely a problem in practice ;)

Risk of deadlock is real if you have processes calling each-other in a cyclic way. e.g. process A sends GenServer call to process B, that then sends a GenServer call to process A t…

> government passes law that requires companies to age verify users > said government provides no way to actually verify a human's age > hilarity ensues

Really cool! You looking to write Elixir as your main job?

This is not a model issue - you just have not properly implemented acoustic echo cancellation on your end.

The truth is this won't actually stop AI crawlers and they'll just move to a large residential proxy pool to work around it. Not sure what the solution is honestly.

Sweet! That's much more reasonable!

$5 to resize 1,000 images is ridiculously expensive. At my last job we resized a very large amount of images every day, and did so for significantly cheaper (a fraction of a cent f…

IMO, it's not. All the UI boils down to: https://github.com/zhangchenchen/query_gpt/blob/main/src/api...

Metal looks super cool, however at my last job when we tried using instance local SSD's on GCP, there were serious reliability issues (e.g. blocks on the device losing data). Has t…

Hoping this leads to datadog launching a logging solution that does not cost an arm and a leg at scale.

Except this article is about how their efforts to prompt the LLM didn't end up working and how they used embeddings / vector search to filter out comments that the LLM generated ba…

Does that matter when you can just swap it for gpt-5-whatever at some point in the future?

Are you implying this technology will remain static in its capabilities going forward despite it having seen significant improvement over the last few years?

I did this measurement, and using time -v, the maximum resident size in KB comes out to 440,424 kb for 1m tasks, 46,820 kb for 100k, and 7,156 kb for 10k.

When I worked at Discord, we used BEAM hot code loading pretty extensively, built a bunch of tooling around it to apply and track hot-patches to nodes (which in turn could update t…

Having a potentially untrusted client connect to the erlang node as a c_node (which seems to be what zerl does) is not a good idea generally, as connecting that way essentially all…

https://github.com/discord/sorted_set_nif

A content-defined chunking scheme allows for you to build a pretty efficient game patcher where you can update between any version of the game (forwards and backwards) and doesn't …

Yeah it just worked a lot better on scylla.

No cache. Just read coalescing. There is a big difference. Coalescing just ensures that while a query is executing if an identical query arrives, rather than sending the same query…

We did not change schema or partitioning strategy.

Scylla just eats all the ram it can with cache. So it's hard to say really. On Cassandra we allocated half the ram to the JVM which it gladly used up and left the other half to the…