Deciphering Glyph, the blog of Glyph Lefkowitz.| blog.glyph.im
Discover comprehensive information on the DNS4EU public resolver services. Compare available options, learn about features, and find answers to frequently asked questions to optimize your DNS privacy and performance| www.joindns4.eu
an AI researcher going back to school for immunology| rachel.fast.ai
In the aftermath of the “AI boom,” this report examines how the push to integrate AI products everywhere grants AI companies - and the tech oligarchs that run them - power that goes far beyond their deep pockets.| AI Now Institute
Tests should contain as little logic as possible. This helps eliminate the test itself as the culprit when a test fails. As a rule of thumb, avoid control flow or conditional logic inside tests.| blog.snork.dev
Going against the common wisdom of “using anyhow for applications”.| Dmitrii Aleksandrov
A book to help translate C++ idioms into Rust.| cel.cs.brown.edu
Exponential backoff with jitter is de rigeur for making service calls. This code, or something like it, probably looks really familiar: func do(ctx context.Context) error { const ( maxAttempts = 10 baseDelay = 1 * time.Second maxDelay = 60 * time.Second ) delay := baseDelay for attempt := range maxAttempts { err := request(ctx) if err == nil { return nil } delay *= 2 delay = min(delay, maxDelay) jitter := multiplyDuration(delay, rand.| commaok.xyz
Yesterday, after playing with some smaller models, I started to experiment with the idea of a flowchart for determining a model’s ancestry with a few prompts. For example, could you ask it about state-censored topics and about its development and figure out what model was it trained by or from. Luckily I aborted that effort, because Sam Paech, who maintains EQ-Bench, has built an entire “slop forensics” pipeline.| Drew Breunig
(Clearly a much better word than simplification.) I believe we generally accept the truth that we should write simple and easy to read code in order to make it harder to create bugs and cause security problems. The more complicated code we write, the easier it gets to slip up, misunderstand or forget something along … Continue reading Decomplexification →| daniel.haxx.se
Multiplying polynomials| eli.thegreenplace.net
