paul-samuels.com

Every now and then when I’m out walking my dog I nerd snipe myself and start thinking of interesting little programming challenges to toy around with.

In this post I explore Swift’s @propertyWrappers and parameter packs to implement a common behaviour.

I spend a lot of time thinking about developer experience at all levels, from what makes a helpful error message deep in a framework to how we make people’s dev environments easy to spin up.

When I’m solving problems I rarely move in a straight line.

Kotlin’s let is a great tool for writing expressive code, but I’ve noticed it can introduce subtle fragility when used the wrong way - especially alongside certain compiler features.

It’s often a red flag if we see duplicated code and we generally try to reduce it as much as possible.

Most of us are familiar with YAGNI (“You Aren’t Gonna Need It”), that old developer mantra reminding us not to add code or functionality until it’s truly needed.

I don’t use a rebase flow on every project, but when I do, here are the habits that help keep things smooth.

Great developer experience isn’t always about polished UIs sometimes it’s as simple as surfacing the right problem at the right time.

I predominantly work in Swift and Kotlin, both of which support default arguments.

Crafting regular expressions is fun - when you nail the incantation you feel like a wizard but as time passes, that once elegant spell can start to look like the output of an Enigma machine.

When a CI job fails, the first thing you usually do is scroll through a wall of logs trying to spot the error.

There’s something oddly satisfying about seeing a piece of physical hardware with its little flashy light brrring along executing some Swift code I wrote to serve requests over the internet.

Retain cycles are often a pain to track down and here’s an example of a less obvious one we had recently.

I’ve been using Kotlin Symbol Processing (KSP) for a few years so I thought I’d reflect on how I like to work with it to stay productive.

SwiftTesting’s parameterised tests are really great.

I’m always fascinated when people build complex things, not so much by the final artifact but by the journey they travelled to get to the end result.

TL;DR Try creating a cli executable in your project that exposes common project tasks that are written in the project’s core language.

I work in a team with many colleagues where we are responsible for several code bases.

I had a case recently where I wanted to migrate an Objective-C class to Swift but as it was a large class.