Harsha Karunarathne

I build web apps that keep working years after launch.

I work on the application side of a project: the logic behind the interface, the services it depends upon, and the maintenance that keeps it healthy once real users are on it. The aim is software that stays predictable as it grows, rather than something that needs rebuilding a year later. That means code the next developer can pick up, systems that fail loudly, and a build that behaves the same as the traffic changes. When something does break, the aim is that it is obvious what broke and quick to put right, rather than a week of guessing.