Early Access Policy
Content Release Model
When a dual feature is released, there’s:
- A video on YouTube
- An article, time-locked for 6 months
- Optionally, some bonus “companion” code to the article/video
Here are examples of dual features:
The article version is accessible in advance for sponsors/patrons of tiers Silver and above (~10EUR + VAT/month)
The bonus code, (like in the virtue of unsynn) is accessible for sponsors/patrons of tiers Bronze and above (~5EUR + VAT/month).
Six months after the video is released, the article automatically unlocks for everyone.
Sponsored Early Access
Generous sponsors are able to buy a time-release for an exclusive article.
This makes the article accessible for everyone immediately, and adds a banner to the article indefinitely to advertise whatever the generous sponsor would like to.
If you’re interested in buying a time-release for an exclusive article, reach out to amos@bearcove.eu directly and we can discuss prices and copy!
For an example of a sponsored early access, check out
Here's another article just for you:
A dynamic linker murder mystery
I write a ton of articles about rust. And in those articles, the main focus is about writing Rust code that compiles. Once it compiles, well, we’re basically in the clear! Especially if it compiles to a single executable, that’s made up entirely of Rust code.
That works great for short tutorials, or one-off explorations.
Unfortunately, “in the real world”, our code often has to share the stage with other code. And Rust is great at that. Compiling Go code to a static library, for example, is relatively finnicky. It insists on being built with GCC (and no other compiler), and linked with GNU ld (and no other linker).