Ledger service
ClientAn event-sourced ledger for a fintech client — postings, reconciliation, and an audit history that has to be exactly right, every time.
I'm Kronos — a software engineer. For about twelve years I've been shipping web apps and the backends behind them, mostly the parts that have to be fast and hold together when everything else is on fire.
A few projects — client and personal. Some details are trimmed for NDA reasons, but the shape is real.
An event-sourced ledger for a fintech client — postings, reconciliation, and an audit history that has to be exactly right, every time.
Real-time dashboard for a logistics company. Streams aggregates over a large dataset and keeps the UI fast without hammering the database.
A small, type-safe query builder for TypeScript. Started it to scratch my own itch; a few other people run it in production now.
A tiny HTTP router that runs on edge workers. Mostly an excuse to learn how isolates and cold starts actually behave under load.
Twelve years across startups and scale-ups, mostly close to the metal where the interesting problems live.
Working with a handful of teams on backend and infrastructure — usually the parts that need to be fast and correct.
Owned the data pipeline behind the product. Moved it to an event-driven setup and spent a lot of time on latency.
Built payment and identity services. Learned how much of the real work is the boring, careful part.
Full-stack across a few early products. Shipped fast, broke things, figured out what holds up.
Tools are means, not ends — but after a decade these are the ones I trust when it matters.
Kronos rebuilt our ingestion pipeline and it has just worked ever since. Easy to hand the hard problems to.
Clear thinker, explains the trade-offs, and the code holds up. We keep coming back with more work.
I take on a few projects at a time. Message me on Telegram, join the channel, or drop an email — I usually reply within a day.