Nix, statistical analysis of build times, and congestion as demand
We look at how one can use Nix to replace some container usage, we statistically analyse build times to get failure rate out, and we learn a useful perspective on congestion.
Off the rhythm this week. Forgot both publishing an article and sending off a newsletter. Well here it is, slightly delayed!
New articles
Using Nix to Try Tools
My new job gives me an opportunity to explore Nix to do things one might otherwise use containers for.
Full article (1-2 minute read): Using Nix to Try Tools
Build Failure Rate from Build Times
The time it takes to complete a build can – perhaps surprisingly – be used to guess how often the build fails! Not that I remember why this would be useful.
Full article (1-10 minute read): Build Failure Rate from Build Times
Flashcard of the week
This flashcard comes from one of those traffic engineering books.
How can we describe congestion?
The answer was really elegant, and it applies just as much to buffering or queuing in computer networks and software system.
The location where excess demand is being stored.
I find it really useful to think of queues as "excess demand" because it makes it more clear when queues don't fix overload and when they do.
Premium subscription
The first premium newsletter went out last week. It had:
- three links to external articles that I thought were really good;
- a two-page review of the first half of Working Backwards: Insights, Stories, and Secrets from Inside Amazon.
- a brief mention of Craft Stories by Chuck Palahniuk and why it matters.
- a preview of what it might look like if one takes The Economist's The World Ahead and tries to squeeze out of it verifiable claims that one can forecast on.
If any of this sounds interesting, you should upgrade to a premium subscription! For a limited time, premium subscriptions are $1/month. As always, you can cancel at any time. To upgrade, click the subscription link at the top of this newsletter and fill in your email again.
Your opinions
As always, I cannot improve without feedback. Reply to this email to share your thoughts on any of the topics above, or anything else!