Building the future,
one line of code
at a time.

From curiosity to craft.

Started writing code in 2006 out of pure curiosity during elementary school and never stopped. From shipping my first real product at school to leading development team at giosg, every step has been driven by a simple belief: software should genuinely help the people using it.

1. 2006

   First line of code

   Wrote my first PHP webpage on Mikro bitti magazine's free web hosting space for subscribers. Realised I could build things that actually worked — and got hooked.

2. 2010

   First shipped product

   Built InfoTV at school to replace an ugly PowerPoint-based system that only worked in IE. Learning what it means to ship something real.

3. 2017

   Nokia internship

   Joined an international team in Espoo building an internal test environment reservation system. Learned Django, MySQL, and what it's like to work across time zones with colleagues in Hangzhou.

4. 2018

   BirdLife — rewriting Tiira

   Civil service turned into a paid role. Helped rewrite Finland's national bird observation service from a static prototype, introduced modern CI/CD, and learned what it takes to build for a mission-driven team.

5. 2019

   Software Engineer at giosg

   Joined a fast-growing SaaS company. Deepened expertise in PostgreSQL performance, helped distribute test execution across multiple nodes, and transitioned into React development after a team restructuring.

6. 2023

   Development Team Lead at giosg

   Stepped up to lead development team. Still writing code, now also helping others do their best work.

Projects I'm proud of.

• 01

  Giosg chat performance

  Diagnosed and fixed slow PostgreSQL queries in a large-scale chat service. Investigated root causes rather than patching symptoms — uncovering improvements that surprised even more senior colleagues.

  50% faster chat assignment to agent · 80% faster chat history listing

  • Django
  • PostgreSQL
  • Python
• 02

  BirdLife Tiira rewrite

  Helped rewrite Finland's national bird observation service from an initial static prototype. Built a mock backend to unblock frontend work, and introduced Mattermost, Gitea, and Drone CI/CD to replace a bare Git server.

  From static prototype to production service

  • TypeScript
  • Aurelia
  • Drone CI
• 03

  Learn Helsinki

  A Duolingo-style quiz game for learning the places and names of Helsinki. A fun side project that scratched a personal itch and ended up being genuinely enjoyable to play.

  Open source on GitHub

  • TypeScript
  • React
• 04

  InfoTV

  Built a browser-based replacement for a school's old PowerPoint info screen that only worked in IE, with WordPress used to manage the content.

  First shipped product, started in 2010

  • PHP
  • WordPress
  • WebSocket
• 05

  Color Wheel

  Created a custom color selector for nanoInkscape, then used the same widget in text editor and photo editor experiments.

  Inspired by Gimp and Inkscape

  • HTML5
  • CSS
  • JavaScript
• 06

  Text Editor

  Built a WYSIWYG editor as a side quest from InfoTV project, learning how tricky rich text editing can be in real browsers.

  Early hands-on browser editing experiment

  • HTML5
  • JavaScript
• 07

  nanoInkscape

  Tried building a small vector graphics editor after discovering SVG support becoming standard on web browsers.

  Very old vector drawing demo

  • SVG
  • HTML
  • JavaScript
• 08

  Pelix

  Wrote a parser, interpreter, and debugger for a small toy language during a personal hackathon in Lapland.

  Reworked the parser after finding performance limits

  • Parser
  • Interpreter
  • Debugger
• 09

  Quicktionary

  Made a small Java dictionary tool while exploring how to turn simple utility ideas into working software.

  Early Java utility build

  • Java
• 10

  Particles

  Experimented with physical calculations and particle-style motion to understand simulation through code.

  Physics and animation experiment

  • Simulation
  • Animation
• 11

  Tmc-cli

  Command line client for TMC (Test my code) server to submit and test exercises for university courses. The application was built practicing collaboration and delivery with other developers.

  University team build

  • Teamwork
  • University
• 12

  Tasker

  Wrote a C-like C++ demo for task management system to showcase my low-level programming skills, beyond web development.

  Systems programming exercise

  • C
  • C++
• 13

  Wren stack overflow bug

  While being interested in how nested functions are implemented in real language runtimes, I spotted a stack overflow bug in wren's for loop implementation.

  Runtime bug fix

  • Debugging
  • Runtime
• 14

  emotion-solid

  Fixed lots of issues in emotion solid package. I was learning solidjs at the time and I wanted to use a familiar styling pattern.

  Frontend styling experiment

  • SolidJS
  • Emotion
  • JavaScript
• 15

  Toy GPU on FPGA

  Spent a Christmas break writing a toy GPU on an FPGA, learning hardware-flavored thinking from the inside.

  Personal hardware exploration

  • FPGA
  • Hardware
• 16

  Thumbnail microservice

  Worked on a thumbnail service, focusing on the kind of backend utility that quietly supports the product.

  Backend service work

  • Backend
  • Images
• 17

  HTML5 front page

  Created an older personal front page as school work in 2011, trying out HTML5 and CSS3 while keeping it viewable across browsers.

  School work that became part of the site history

  • HTML5
  • CSS3
• 18

  The Hero

  Built a WebGL hero background with a draggable procedural planet, star field, and moon. This was my first partially vibe-coded personal that I actually published.

  Interactive landing hero for this site

  • TypeScript
  • JavaScript
  • WebGL

The right amount of process
for each problem.

1. 01

   Understand

   Clarify the problem from the stakeholders. See where the request is coming from. Think deeply what is the best solution for the problem without causing more problems than it solves.

2. 02

   Design

   Sketch the user interface for the solution. Consider the internationalization and customer specific setups when writing the ticket for the feature.

3. 03

   Build incrementally

   Ship small, working pieces if feature is large enough. Don't over-engineer the solution. Don't overwhelm the reviewer(s) with the code changes.

4. 04

   Refine

   The first version doesn't need to be perfect. Measure, learn, and iterate. Leave every codebase cleaner than you found it.