Oskar Wickström

Disclosure: I’m the original author and lead for the Bombadil project at Antithesis.

About three months ago, I bought the Onyx BOOX 25.3” Mira Pro Color, an e-ink monitor for desktop use.

One neat thing about Bombadil’s specification language is that it’s plain TypeScript, with access to external NPM packages.

Last week at Bug Bash 2026, I had a bunch of interesting discussions about testing non-web interfaces with Bombadil, our new property-based testing framework for user interfaces.

Today I’m announcing and open-sourcing the Bombadil project — a brand new property-based browser testing framework.

Quickstrom is a property-based testing tool for web applications, using QuickLTL for specifying the intended behavior.

I’ve been hinting on X/Twitter about my use of the Daylight DC-1 as a programming environment, and after about a year of use, it’s time to write about it in longer form.

Amp is a coding agent which I’ve been working on the last six months at Sourcegraph.

This last month has been fascinating.

Recently, I published The Monospace Web, a minimalist design exploration.

In the eternal search of a better text editor, I’ve recently gone back to Neovim.

Lately I’ve been messing around with Python 3.12, discovering new features around typing and pattern matching.

Quickstrom uses linear temporal logic (LTL) for specifying web applications.

In October 2020, we got our new house.

In the last post I shared the results from testing TodoMVC implementations using WebCheck.

In this post I’ll share the results from testing TodoMVC implementations using my new testing tool named WebCheck.

Property-based testing (PBT) is a powerful testing technique that helps us find edge cases and bugs in our software.

In the last article we looked at how Komposition automatically classifies moving and still segments in imported video media, how I went from ineffective testing by eye to finding curious bugs using property-based testing (PBT).

In the previous case study on property-based testing (PBT) in Komposition we looked at timeline flattening.

In the first post of this series I introduced the Komposition screencast editor, and briefly explained the fundamentals of property-based testing (PBT).

This is the first in a series of posts about using property-based testing (PBT) within Komposition, a screencast editor that I’ve been working on during the last year.

Haskell at Work, the screencast focused on Haskell in practice, is approaching its one year birthday.

For the last six months I’ve been working on a screencast video editor called Komposition, and it’s now released and open source.

This post introduces a declarative GTK+ architecture for Haskell which I’ve been working on during the journey with FastCut, a video editor specialized for my own screencast editing workflow.

In the first part of this series, we left off having made states explicit using Haskell data types.

Stateful programs often become complex beasts as they grow.

While writing my talk “Finite-state machines?

Writing technical presentations that include code samples and diagrams can be really tedious.

I have experimented with a test language encoded in tagless final style, instead of algebraic data types, to support the typed combinators beforeEach and beforeAll.

Since laying Oden aside, I have been getting back into PureScript, and started working on a project called Hyper that I would like to introduce you to.

I have decided to stop working on Oden.

I have worked intensively on the Oden User Guide lately, primarily on improving content, but also on providing high-quality PDF and HTML output formats with detailed control over typesetting.

Having tried a lot of color schemes for editors, especially for Vim, I have gotten quite picky.