Why a specific stack was chosen
The decision, the alternatives that were rejected, and the constraint that settled it.
Engineering notes
Lessons that outlive the project.
Short technical records: why a stack was chosen, an integration that failed, a platform limitation discovered the hard way. This section becomes the Lab's practical knowledge base.
Published notes
Nothing published yet.
The knowledge base is empty
Notes are written one at a time, usually right after something breaks. The categories below are the shape this section will take.
Planned topics
What belongs here.
Every note answers one question and stays short enough to actually get written.
A failed integration
What did not connect, why, and what was used instead. Failures are cheaper to read than to repeat.
Google Apps Script limitations
Quotas, execution ceilings and the point where a script should become a real backend.
Supabase decisions
Row Level Security defaults, policy design, and what breaks when RLS is left off.
A useful Claude workflow
Prompts, guardrails and review steps that made AI-assisted coding safe rather than fast-and-broken.
A performance finding
A measurement, what caused it, and the change that moved the number.