Improving Elm PRNG
A bug is uncovered in the de facto PRNG library in the Elm language ecosystem and alternative PRNG algorithms are suggested.
A bug is uncovered in the de facto PRNG library in the Elm language ecosystem and alternative PRNG algorithms are suggested.
where delays are shown to be counterintuitive.
In my mind there’s a spectrum going from 0.00 - “all manual” (where we all were a few years ago) to 1.00 - “vibe coding” (you’re a product manager and don’t look at any code at all, just spamming “XYZ doesn’t work for me, fix it”).
After reading the book The AWK Programming Language (recommended!), I was planning to try AWK out on this year’s Advent of Code. Having some time off from work this week, I tried to implement one of the problems in it to get some practice, set up my tooling, see how hard AWK would be, and… I found I’m FP-pilled.
This is my Code BEAM Europe 2025 talk, converted to a blogpost.
Today’s story begins in the Elm Slack, where I saw a RSS integration post a notification about a new package:
TL;DR: turn off automatic updates then flash an older firmware via LPR over the network.
…in which I’ll tell you how you can make sure your property based tests are testing the interesting cases.
First of all, this blogpost is kinda long. Let me prove to you reading it will actually have some payoff:
I’m writing this on the plane from London to Prague, as we’re waiting for delayed takeoff due to thunderstorms over Czech Republic. (EDIT: A day later, I’m now finishing this on my couch back in Ostrava.) I’ve spent an amazing week in the English countryside, among roughly 40(?) Elm-minded folks. Many of them are people I interact with almost daily on the Elm Slack or the Incremental Elm Discord,…