I got into computer science by wanting to know what happens one layer down — the data structure under the app, the OS keeping it alive, the infrastructure letting it scale. I still learn the same way I started: build a small thing, break it on purpose, and stick around long enough to understand why it broke.

Not a portfolio — just a couple of things I couldn't leave alone.

Instagram Unsend  ·  python · playwright A human-supervised tool that bulk-unsends your own Instagram DMs — it detects messages live, checks you actually own one before touching it, and stops the instant you change your mind.

MovieTracker  ·  swift · swiftui An offline-first iOS app for tracking films — watchlist, ratings, reviews, and a stats dashboard, built on a clean, fully-tested MVVM core.

The rest is usually mid-build. The good ones start as experiments I can't put down.

Away from the keyboard I'm usually gaming, running through far more music than is strictly reasonable, or getting pulled away by Teatu — my dog, and the one reviewer here who stays completely unimpressed by any of it.

name:    Teatu
role:    Chief Distraction Officer
reviews: zero pull requests, infinite interruptions
verdict: worth every single one

known bug: occasionally rewrites working code just to see how it works. wontfix — that's kind of the whole point.

_{a year of building, traced one commit at a time.}