Lloyd Logs

Logging the things I am learning, breaking, fixing, and building.

Logs

  1. Building a Time Tracker in Zig Instead of Go

    Thyme proved that automatic time tracking works as a CLI. Turning it into a native Linux desktop app pushed the project out of Go and into Zig.

  2. Rebuilding Lloyd Logs as a Go Markdown Site

    Replacing a static Hugo setup with a small Go server, Markdown content, Docker deployment, and an Obsidian-friendly publishing workflow.

  3. Idempotent ERPNext Seed Data for a Real SaaS Business

    A repeatable ERPNext seed-data workflow for business objects like plans, cost centers, issue types, and onboarding tasks without faking customers or invoices.

  4. Adding Observability to a Small SaaS Without Overbuilding It

    A small observability stack that focuses on useful signals first, with health checks, canaries, error tracking, and alert routing that a small team can actually maintain.

  5. GitOps Promotion for a Small SaaS: From Image Build to Production Rollout

    A small, repeatable GitOps promotion flow that moves an image from build to staging to production without depending on manual deployment steps.

  6. Designing a Guest Ordering Flow That Balances Speed, Clarity, and Admin Control

    A guest ordering flow shaped around speed and clarity, while still letting admins control the modes and menu presentation rules that affect the experience.

  7. From Messy Menu Imports to Safer Data Modelling for Hospitality SaaS

    A practical pass over the messy reality of hospitality menu data, with validation, duplicate handling, recovery UX, and safer handling of incomplete pricing.

  8. Integrating ERPNext Helpdesk Into a Multi-Tenant SaaS Without Leaking Tenant Data

    A support gateway pattern that keeps tenant data separate while a SaaS app talks to ERPNext Helpdesk in a controlled, auditable way.

  9. Building a Payments Integration Layer That Keeps Venue Owners in Control

    A payments layer that keeps venues in control of payouts, refunds, and fees while the SaaS platform stays out of the funds flow.

  10. Moving Business Logic Out of the Browser in a React and Go SaaS

    A boundary-focused rewrite that moved trusted business decisions out of React and into Go services so the browser handled presentation, not authority.

  11. Designing Multi-Tenant Authorization With Supabase RLS and Role Boundaries

    A database-first approach to tenant isolation for a hospitality SaaS, with roles, helper functions, testing, and the failure modes I try to design out early.

  12. Recovering a Broken React Deployment Without Guesswork

    The loader stayed visible, the hero never rendered, and the canary started failing. The problem looked like a broken React build. It was three problems pretending to be one.