Personalized learning paths: the system suggests, the learner decides what to study
How I designed a diagnostic-driven learning path for corporate training, and why leaving the final call to the learner is consistent with andragogy.
// cat ./blog/*.md
Notes on Laravel, architecture, infrastructure and what I learn while building products.
filtering by #laravel clear
How I designed a diagnostic-driven learning path for corporate training, and why leaving the final call to the learner is consistent with andragogy.
How each Markmedi clinic sends campaigns from its own domain, with aligned DKIM, continuous DNS verification, an isolated queue and bounce handling via SNS.
Why Markmedi has its own analytics layer, with a closed list of events, typed props and daily aggregates, and why no third-party tag runs inside the app.
Row-level tenancy with a global scope, per-clinic RBAC, audit trails, hardened uploads and a Sentry that never sees personal data: the security decisions behind a healthcare SaaS.
How Markmedi's calendar, waiting list and consultation room update themselves with Reverb, without sending patient data over the WebSocket and revoking access without presence channels.
About 7,000 Pest test cases, architecture tests, a browser suite in four shards and CI jobs that spin up real MySQL, Redis and Supervisor.
33 bounded contexts, Actions, enum state machines, ports and adapters and after-commit events: how I organized a large SaaS so that one person can maintain it.
Fixed-capacity supervisors, tested timeout invariants, a global rate limit for SES and an idempotency ledger: how I organized Markmedi's queues with Laravel Horizon.
Temporary slot holds, a pessimistic per-clinic lock, idempotency keys and race tests against a real MySQL: how I solved concurrency in Markmedi's scheduling.