About
I'm Shijil. I build software I use myself, which turns out to be the strictest form of quality control there is — every shortcut comes back to me personally.
LifeOS started from a simple frustration: the things worth tracking over years — what a vehicle actually costs to run, where money goes, which habits hold — end up scattered across notes apps, spreadsheets and memory. None of those answer a question asked two years later.
So it is built as a record system first. Every module writes structured, queryable rows. Dashboards and analytics are readers of that same substrate, never the source of truth. You can always add a view over good data; you can never recover data that was never modelled.
A few rules make it hold up. Quantities are stored as integers in their smallest unit, so money and distance never drift. Derived numbers are computed on read, never cached, so a stale average can't quietly contradict the rows behind it. And nothing is ever hard deleted.
It is a product I intend to use for years, so the bias is always toward the decision that is still correct at year five rather than the one that is quickest this afternoon.
How I work
- Plan first, then design the data, then the interface, then build feature by feature.
- Write down the reasoning, not just the result — the “why” is the part that decays.
- Prefer boring, long-lived dependencies over pleasant, short-lived ones.
- Ship something usable daily; improve it continuously.