Software Architecture

An architecture diagram can make every boundary look clean. Deployment reveals where the real boundaries are. With TimeSense, production work exposed issues that were easy to miss in isolation…

TimeSense uses FastAPI, PostgreSQL and Redis/Celery, but not because they form a fashionable stack. Each component solves a different problem. FastAPI provides typed API contracts and works well with…

One of the most important corrections I made in TimeSense came from using the app on a real device. Calendar meetings were initially represented too much like tasks. That created contradictions…

TimeSense uses an LLM, but the LLM is not the entire architecture. The system first gathers structured context: calendar commitments, tasks, routines, sleep, meals, commute signals, deadlines and…

TimeSense could easily have become another task manager. Projects, boards, labels, categories, drag-and-drop scheduling and complex routines all sound useful in isolation. Together, they would…

One of the first decisions I made with TimeSense was to build it as a true native mobile app rather than place a web application inside a mobile wrapper. I considered a cross-platform framework…