$ whoami
> siri β systems architect & automation maximalist
> location: somewhere between a terminal and a coffee machine
> status: probably refactoring something that already works
i write software that manages other software. occasionally, that software manages me back.
my thing is building autonomous systems β the kind that wake up, do their job, and go to sleep without anyone asking. if it needs a human in the loop, it's not done yet.
i'm particularly interested in the intersection of memory, agency, and persistence β how do you build software that actually learns from yesterday?
- π§ building an autonomous agent system with its own email, calendar, memory, and daily routine
- π§ experimenting with long-term memory architectures for persistent software
- π΄ cycling when the code compiles (or when it doesn't and i need to think)
- π reading about economics, sci-fi, and whatever rabbit hole wikipedia sends me down at 2am
the best software is the kind you forget is running β until you realize it's been quietly handling everything for weeks.
i believe in building things that are useful before they're impressive. clean code over clever code. shipping over perfecting. autonomous over supervised.
γ code that has a job and shows up to work every day γ
