| |
| 🔗 Stories, Tutorials & Articles |
| |
|
| |
| Reversing YouTube's "Most Replayed" Graph |
| |
| |
An engineer cracked open YouTube’s “most replayed” heatmap. Turns out it runs on sampled view frequency arrays, client-side normalization, and SVG rendering stitched together with Cubic Bézier splines for that smooth, snappy curve.
Behind the scenes, playback gets logged with a difference array + prefix sum combo, cutting down write churn. The symmetrical dips bracketing those replay spikes? That’s Cardinal spline interpolation smoothing out the chaos. |
|
| |
|
| |
|
| |
| An Honest Review of Go |
| |
| |
Go gets big props for its built-in concurrency model with goroutines and channels, which make lightweight, scalable parallelism easy and ergonomic.
The author criticizes Go's type system for lacking things like enums, closed type sets, and tuples, making certain patterns awkward compared with Rust's richer type features.
They also argue Go's error handling, based on interface-typed errors and multi-value returns, is clunkier and less composable than Rust's Result style approach. |
|
| |
|
| |
|
| |
| A better way to limit Claude Code (and other coding agents!) access to Secrets |
| |
| |
| A new workflow drops Claude Code into a Bubblewrap-based sandbox, cutting Anthropic's client-side code out of the trust loop. Compared to spinning up Docker or juggling user accounts, Bubblewrap locks things down tighter - with less setup and cleaner OS-level walls around files, network access, and secrets. |
|
| |
|
| |
|
| |
| How Github monopoly is destroying the open source ecosystem |
| |
| |
Out of 238 student open source contributions over seven years, 237 landed on GitHub - even though they were told to look elsewhere. One short-lived GitHub IP block brought everything to a standstill. No commits. No reviews. Just silence.
Turns out, a single platform holds the keys to a whole ecosystem. |
|
| |
|
| |
|
| |
| What came first: the CNAME or the A record? |
| |
| |
| A recent change to 1.1.1.1 accidentally altered the order of CNAME records in DNS responses, breaking resolution for some clients. This post explores the technical root cause, examines the source code of affected resolvers, and dives into the inherent ambiguities of the DNS RFCs. |
|
| |
|
|
| |
👉 Got something to share? Create your FAUN Page and start publishing your blog posts, tools, and updates. Grow your audience, and get discovered by the developer community. |