Software that works.
In production.

Bringing the User Back from Mobile BankID on an iPhone

Logging in with Mobile BankID on a phone goes like this: you tap "Open BankID" in the browser, the BankID app opens, and you identify yourself. Then, by default, you are left in the BankID app, and you have to go back to the browser yourself. Not a nice experience. We wanted LogEze to bring the user back to the browser without that extra step.

Run Your Coding Assistant in the IDE Terminal

For a long time I ran my coding assistant in a separate terminal window. Claude Code or Mistral Vibe on one side of the screen, IntelliJ on the other. It worked, but I had to switch windows to see what the assistant had done, and then find the files it had touched. More often than I like to admit, I didn't bother. I read the summary in the terminal and moved on.

Characterization Tests: A Safety Net Before You Refactor Legacy Code

You want to refactor a class and the tests you were counting on are not there. Or they are there, but they aim somewhere else and none of them would notice if you got this particular piece wrong. The code works, presumably, since it has been in production for years. You just have no way to prove that it still works once you have touched it.

Characterization tests are for this situation. You write tests that describe what the code does right now, and then you refactor with those tests watching your back.