Experiment · Article · Code
Last Seat Lab
One shared seat, competing clients, and experiments in transactions, authorization, durability, and realtime state.
CS student
Building · Writing
I'm Ullas. I build things, follow the questions they raise, and write down what I learn.
Lately, I've been exploring how applications keep shared data correct when requests compete, connections drop, or servers restart.
Selected work
A place to beginOpen-source contribution · Open
PostgreSQL error logging in SpacetimeDB
A focused change that keeps 4xx responses at warning level and records 5xx server failures as errors, backed by a regression test.
Personal note
From nineteen to twenty
On leaving home, learning to build, and not letting ambition rush me past my own life.
Latest writing
3 pieces
Technical Writing
Last Seat on Kubernetes: what keeps running, and what stays correct
I moved my one-seat booking lab onto a local Kubernetes cluster, then killed databases and servers on purpose to see what Kubernetes guarantees and what it leaves to the database and the code. Technical WritingLast Seat Lab: Exploring databases and realtime synchronisation
What one shared seat taught me about transactions, realtime synchronisation, caller identity, and keeping one authoritative database truth. NotesFrom nineteen to twenty
On leaving home, learning to build, and not letting ambition rush me past my own life.Sections
Say hello
Have an idea, a question, or something you're working on? I'd like to hear from you.