Principal software engineer / Builder & writer

Good software.
A little soul.

I’m Dilusha, a principal software engineer. I’ve been building software professionally since 2012. Still curious enough to lose track of time making something work.

I help founders and small teams fix stubborn bugs, connect AI to useful workflows, and get web apps ready for the real world. Available for focused, part-time freelance projects.

Node.js / TypeScript / React / AWS / AI integrations

Engineering since 2012

Calendar time from 1 January 2012.

The landscape from my original corner of the webAn observatory for ideas.
A note to myself{dilusha}
2,121 thoughts to wander through
Dilusha GonagalaEngineer. Writer.
Still figuring things out.

01 / The workshop

Something stuck?
Let’s move it forward.

A clear problem, a manageable scope, and someone who cares about the details.

A few connected obsessions

Follow what
pulls you in.

Useful software, unlikely beginnings, and questions I haven’t finished asking. Pick a point on the map.

From the notebook / Where it began

Windows 95. Around 64 MB of RAM.

My first computer, in 2004. That’s where my engineering journey began.

By around 2006, I was making a calculator out of roughly 2,000 PowerPoint slides, before I understood what programming was. Seventeen hours later, it worked.

Experience / Behind the interface

The work
underneath.

A few problems I’ve worked through, across professional systems and my own products.

Financial systems

Getting statements out on time.

I worked on a credit card statement-processing system that was struggling to finish within its processing window. I helped scale the system and fix processing problems so it could handle more work.

That experience shaped how I approach reliability: the job has to finish when people depend on it. Company details, volumes, and implementation specifics stay private.

AgentsEye / Integration & reliability

Making usage alerts trustworthy.

AI coding providers report limits and reset windows differently. In AgentsEye, I brought those readings into one native Mac app, with local history and alerts that account for quota resets.

The details matter: an alert must distinguish a new usage cycle from continued consumption. I also built the widgets and signed update path needed to keep the app useful beyond its first install.

Links on Link / Commerce

Connecting the storefront to the sale.

For Links on Link, I built across the public page, creator dashboard, payments, and digital delivery. A storefront needs those pieces to agree about what someone bought and what they should receive.

That meant working through Stripe integration and verified payment webhooks alongside custom domains and campaign analytics. The interface is one part of the system that supports it.

The person behind the pull request

It started with a calculator.
In PowerPoint. Seriously.

I spent 17 hours making it work, before I even knew what programming was. That feeling never really left. Since then, my work has taken me through equipment manufacturing, e-commerce, and fintech.

This site is also where I think out loud about life, kindness, books, and the messy middle of making things. There’s room for all of it here.

A little more about me

02 / The notebook

Things I’m
thinking about.

Open the whole notebook

A good place to start

Tell me what
you’re working on.

A bug that won’t quit? An integration you haven’t had time for? Start with the problem. We’ll work out the next step.

Find out how we can work together