Field notes

Better business systems, explained.

Practical thinking on broken workflows, useful automation, reliable software, and the work required after launch.

EngineeringSep 11, 20264 min read

A contact form that depends on email will lose leads silently

If sending the email is the only thing your form does, then an unset API key deletes the submission and shows the visitor an error. Separate capture from notification and the failure costs a notification instead of a lead.

Diego González ZapiainRead →

EngineeringSep 11, 20264 min read
Your rate limiter is probably counting the wrong requests
If the limiter runs before validation, a visitor's own typos spend their allowance and their next correct submission is silently discarded. The order of honeypot, validation and limit decides who pays.
Read entry
EngineeringSep 11, 20264 min read
Two Supabase mistakes that fail silently, and how to catch both
A camelCase column breaks every insert with PGRST204. Supabase's new API keys are not JWTs and belong in the apikey header. Neither mistake has to surface in your app.
Read entry
ThesisApr 12, 20262 min read
Why small expert teams can now deliver complete business systems
AI can compress implementation time. The real advantage is giving experienced builders more time for workflow design, testing, and accountable delivery.
Read entry
CraftApr 10, 20262 min read
How LOJIK moves quickly without making the client the test team
A practical delivery loop for turning one broken workflow into reliable software, clear ownership, and a supported launch.
Read entry
CraftApr 8, 20262 min read
Designing a WhatsApp-first appointment system for Mexican clinics
A clinic does not need another chatbot. It needs a complete appointment workflow that handles language, calendars, exceptions, privacy, and human escalation.
Read entry
EngineeringApr 5, 20262 min read
A premium interface still has to explain the product
Motion and visual polish can earn attention, but conversion depends on clarity, useful hierarchy, fast performance, and an obvious next step.
Read entry

Built by LOJIK

Things we built. Samples of what we can build for you.

We built these for ourselves first. What we build for you is shaped around your business.

Things we build

Apps
Internal tools
Automations
Integrations
Customer portals
AI agents

Explore our work

Intertitle development preview · demo profile
AvailableIntertitleYour film diary, with recommendations shaped by your own taste.
Maestro development preview · synthetic session data
In developmentMaestroA coach for music producers that follows your live session and suggests what to try next.
In developmentTemperA fitness coach for iPhone that keeps your plan, workouts and meals in one daily routine.

A contact form that depends on email will lose leads silently

Your rate limiter is probably counting the wrong requests

Two Supabase mistakes that fail silently, and how to catch both

Why small expert teams can now deliver complete business systems

How LOJIK moves quickly without making the client the test team

Designing a WhatsApp-first appointment system for Mexican clinics

A premium interface still has to explain the product

Things we built. Samples of what we can build for you.

A contact form that depends on email will lose leads silently

Your rate limiter is probably counting the wrong requests

Two Supabase mistakes that fail silently, and how to catch both

Why small expert teams can now deliver complete business systems

How LOJIK moves quickly without making the client the test team

Designing a WhatsApp-first appointment system for Mexican clinics

A premium interface still has to explain the product