Thomas Visser

I wrote a post about some of the work I’ve been doing at NewStore: Our Shopping App platform is powering 40+ shopping apps across iOS & Android, trusted by brands and rated five stars by millions of users worldwide. […] When we started out, we did the log…

I wrote a post about some of the work I’ve been doing at NewStore: “In this post we’ll discuss two multi-agent tools: A Slack-bot that helps us triage reported issues with our shopping apps A research agent that helps us respond to incidents […] Our first…

I wrote a post about some of the work I’ve been doing at NewStore: “Our platform is delivering 20+ shopping apps, trusted by brands in 40+ countries and rated five stars by millions of users worldwide. […] We have to be smart about what we test in the app…

I wanted to watch a video about robots with my 5-year-old son.

With all the recent developments around large language models (LLMs) like GPT-4, discussions about artificial general intelligence have sparked again.

As the author of BrightFutures, a somewhat popular implementation of Futures & Promises in Swift, I felt obliged to take a look at Combine’s Future type and see what first party support for these concepts is like.

A question on Twitter prompted me to think about why Combine has so many implementations of the Publisher protocol.

Here’s a different way of implementing a Set in Swift: struct Set<Element: Equatable> { var contains: (Element) -> Bool } You can initialize an instance like this: let set = Set<Int> { $0 == 42 } And test for membership like so: set.contains(42) //…

I’ve long accepted that breakpoints in Xcode move in ‘mysterious ways’.

I was looking into why videos wouldn’t autoplay inside a WKWebView and couldn’t find a comprehensive up-to-date answer online.

If you’re writing unit tests and use helper methods to factor out common assertions, you might have encountered situations where test failures would not show up in the correct location in your Xcode editor.

Dependency injection is a design pattern where types explicitly declare their dependencies and allow them to be set from the outside.

The MVVM architecture and the Reactive Programming paradigm can be combined to form a very pleasing approach to iOS app development.

How do you make sure related code in different places is kept in sync?

Let’s write a minimal Reactive program.

The topic of this post is weirdly specific for a first post on RxSwift, but it’s a good a start as any.

Ten days ago, I wrote a post about asynchronous values as first-class citizens in Swift.

Update (December 6, 2015): Swift is now Open Source.

Last week, I gave a talk at Swift Summit in San Francisco wherein I live coded a minimalistic Futures implementation based on BrightFutures.