Martin Janiczek

I want to quickly comment on a change in myself I was observing for the past few months.

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!)

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: I do love PBT-testing data container libraries against the “spec” when given the opportunity, and since I created myself a small tool called elm-…

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.