Notes

Short notes on what I'm building, what broke, and what I learned from it. Written as it happens, not cleaned up afterwards.

  1. The ticket to the next roomTen days after writing about the four walls, the system started holding itself up. This is about the part nobody warns you about: keeping your head straight when it finally works.
  2. My four walls and the search for momentumTen months in twelve square meters. Not a story about focus as a virtue, but about removing every exit until the work was the only one left.
  3. Two days in Tampere, and you do not need an ideaI found my name on the mentor list for a hackathon for upper secondary students. If you are one, go, and here is why I am saying that plainly.
  4. A new chapter starts when the tests go greenSelda is in production. Ten months of work, and the first campaigns go out this morning.
  5. Eight thousand commits since the last postMy last post anywhere was two and a half years ago. I was busy putting things back in order.
  6. First time at JunctionI got in. I have spent years deliberately avoiding this kind of thing.
  7. Closing the channel to save your own timeSomeone told me they were removing digital ways to buy so the process would take less of their time. It works, eventually.
  8. If I have to book a demo, I am not your customerTwo rules I have built every product against, and what a booking vendor taught me about both.
  9. Fifteen versions of the same screenCharts you did not configure yourself are not information. They are stress.
  10. Three and a half months on one problemWriting a message that sounds like a person and still converts. The hardest thing in the product, and not a technical problem.

Get an email when a new note goes up. Nothing else, and an unsubscribe link in every message.